Seven data layers per asset, on a continuous schedule.

Continuous monitoring isn't a marketing word. Every asset in your inventory is scanned across seven independent data layers, on Deepinfo's schedule (not yours), with full historical state preserved per layer. When something changes (DNS modified, certificate rotated, port opened), the platform surfaces the delta as an event.

WHAT THIS DOES

Continuous coverage across the dimensions an attacker would look at.

Every monitored asset is scanned across seven independent data layers: Whois, IP-Whois, DNS, SSL, port scan, HTTP, and web data. Each layer captures a different attack-relevant view of the asset: registration metadata, network ownership, live DNS records, certificate state, exposed services, web technology fingerprints.

Scanning runs on Deepinfo's continuous schedule. Your team doesn't trigger scans, doesn't manage cadence, doesn't worry about scan windows. The data refreshes automatically; new findings show up in your dashboard and alerts as they're discovered.

Full historical state is preserved per layer. Every DNS record, every certificate, every open port. Versioned over time. When you investigate why something happened, the change history is right there.

HOW IT WORKS

Three mechanics that make continuous actually mean continuous.

Each layer scans on its own schedule. Drift is detected as discrete events. History stays queryable.

Seven independent layers per asset.

Whois (registration), IP-Whois (network ownership), DNS (live records), SSL (certificate state), port scan (exposed services), HTTP (response headers, redirects, security headers), web data (technology fingerprinting, login page detection, screenshots). Each layer scans on its own schedule.

Drift detection on every change.

DNS records change. Certificates rotate. Open ports shift. Web technologies update. The platform tracks deltas continuously and surfaces them as discrete events: SSL changed, Whois changed, DNS changed, new open port detected, new asset discovered. Alerts route to where your team works.

Full historical state.

Every layer's data is timestamped and versioned. When investigating an incident, you can see the asset's state at any point in time. When passing audit, the full change history is exportable. When something breaks, the diff makes the cause obvious.

WHAT IT SURFACES

Examples of what continuous scanning actually catches.

New subdomains

Appearing on the asset. Subdomain enumeration on every scan.

Certificate rotations

New issuers, expiry changes, hostname additions and removals.

Open ports

Opening or closing on the asset.

DNS record changes

New MX servers, TXT record modifications, NS changes.

Web technology updates

Detected via HTTP response and content fingerprinting.

Whois ownership changes

May signal asset transfer or takeover.

PART OF EASM

Scanning feeds everything else.

Continuous Scanning is the engine that powers the rest of EASM. Every detected change feeds risk detection (Comprehensive Risk Detection), every CVE found gets enriched with EPSS and CISA KEV (Complete Risk Scoring), every issue gets tracked through a nine-state lifecycle (Remediation with Actionable Insights). The discovery pass (Smart Asset Discovery) feeds new assets in; scanning takes them from there.

← Back to EASM

“Quarterly scans were the baseline when I started in security. Continuous scanning across seven data layers, with full historical state, means we catch drift the day it happens, not at the next assessment cycle.”

— Head of Security, Healthcare System
SEE IT IN MOTION

Watch your attack surface change over time.

Run Deepinfo against your domain. The free threat exposure report shows current state; the EASM module monitors continuously after.

Request a demo