CyberSpec
Start free scan

Network scanningLIVE

On-demand and scheduled scans against domains, IPs, and CIDR ranges, with live progress and CVE correlation.

A scan is only useful if you trust what triggered it and can see it happening. Every scan runs in an isolated, short-lived worker against a target you've verified ownership of and consented to scan — domain via DNS TXT or a well-known file, IP/CIDR via attestation against an already-verified domain. Findings write incrementally as they're discovered, so a scan's progress page shows real results building up, not a spinner until it's done.

  • Quick, full, and custom scan types against domains, IPs, and CIDR ranges
  • Scheduled recurring scans (cron-style) so drift gets caught automatically
  • Live scan progress, not poll-and-refresh
  • CVE correlation via vulnerability-scripted nmap, not just an open-port list

Nothing gets scanned until you prove you own it

Unauthorised scanning is a legal problem, not a feature gap. Every asset has to clear ownership verification before its first scan: a domain via a DNS TXT record or a file at a well-known path, an IP or CIDR range via attestation tied to a domain you have already verified. Scanning also requires accepting a per-asset authorisation agreement. It is a few extra minutes on setup and it is the reason you can point this at production without a conversation with legal first.

Scheduled scans catch the drift a one-off scan cannot

Exposure is not a static property. A load balancer config changes, a dependency upgrade opens a port, someone ships a service that was meant to be internal. Cron-style recurring scans run on whatever cadence each asset deserves — weekly on the things that change constantly, monthly on the ones that do not — and only one scan runs per asset at a time, so a slow full scan never stacks up behind a scheduled one.

Live progress, and results that appear as they are found

Scan progress streams in real time rather than being polled, and findings are written incrementally as they are discovered. You can start triaging the first critical finding while the rest of the port range is still being swept. Every scan lands in a history with an explicit status — queued, running, completed, failed, or cancelled — so a scan that died is visibly a scan that died, not a silently missing result.

Start free scan

Explore the rest of CyberSpec