Vulnerabilities and exposure

"Exposure" is everything on the outside of a domain that an attacker could use: a known vulnerability in software the site runs, a service listening on a port it should not, a secret in a public file, a host nobody remembered. DomainGuard finds it with a container of open-source scanners plus its own checks, never scans a domain the account has not shown it owns, and labels every verdict by the evidence behind it.

Articles

• Exposure scans: profiles, tools and limits - quick, standard, deep, port-scan and extreme; what each runs; the manual allowances and the opt-in schedule.
• Verifying a domain for deep scans - basic scans run on any domain; deep scans need the domain verified (email link, DNS record or file, about a minute, re-checked for you), a sign-in email at it, or account approval; protected targets.
• Findings, carry-forward and dismissals - severity, what a finding shows, why a lighter scan cannot clear a heavier one's findings, and the four dismissal reasons.
• Hosts and open ports - every host found, its services named by what the port means, and the 134-port list.
• Software inventory and vendors - what a scan proved the site runs, split into versioned and only-seen, with confidence and the detector.
• KEV and CVE alerts with verdicts - the feeds, watch-forward alerting, and the four exposure verdicts.
• The software watchlist - track a product for new advisories, sources and severity filter; site versus device software.
• WordPress plugin and theme checks - what a scan reads from a WordPress site, the keyless advisory lookup on exact versions (WPVulnerability.net and WordPress.org), and the XML-RPC and readme checks.

Where

• Web: Security (Overview, Vulnerability scan, Network targets, Impostor domains) for scans and hosts; Software (Your software, Advisory feed, Service status, Scan readings) for what you run and the advisories against it.
• iOS: a domain's Vulnerabilities module (Findings, Hosts, Software & services); Monitoring, Software for the account-wide list, and under it More, Advisories, hosts and network targets for the full workspace (Alerts, Software, Hosts, Watchlist, Software catalog, Site scan findings, Advisory feed).
• API/MCP: /api/vuln-scan/*, /api/vulnapps/*, /api/scan/ports/:id; the vulnscan scope.

Common questions

Is a scan safe for my site? The templates are non-intrusive reads and the port probe is a connect test. Nothing exploits, writes or floods, and the scanners run only on domains the account has shown it owns.

Why does my domain say "0 findings" after only a Quick scan? A Quick scan reads what the site serves and nothing more. Run Standard for the active checks; the page says which profile ran.