Why does "Cross Signal Scan Coverage Limited" appear in ExposureGrid?

Scanners observe externally visible signals. A finding means our rules matched - validate severity and applicability in your environment.

Could this be a false positive?

Yes, depending on context and coverage limits. Especially for heuristic, partial, or pattern-based checks, corroborate with manual review.

Re-run a scan to confirm the external signal changed, then enable monitoring where your plan supports it.

Cross Signal Scan Coverage Limited: what it means, why it may matter, and how to remediate with external verification using ExposureGrid.

Cross Signal Scan Coverage Limited: Multiple external findings may combine into higher-risk attack paths even when each item seems minor alone.

Correlation helps prioritize - still validate each ingredient finding on its merits.

Review linked findings across DNS, TLS, ports, headers, and applications together.

Fix external exposures first (ports, leaked origin, dangling DNS), then narrow app-level issues.

Run a scan to verify this fix on your domain

Use the same public scanner as the homepage — results honor your plan tier.

ExposureGrid highlights clustered risk themes while respecting entitlement and redaction.

Why does "Cross Signal Scan Coverage Limited" appear in ExposureGrid?: Scanners observe externally visible signals. A finding means our rules matched - validate severity and applicability in your environment.
Could this be a false positive?: Yes, depending on context and coverage limits. Especially for heuristic, partial, or pattern-based checks, corroborate with manual review.
What should I do after changing configuration?: Re-run a scan to confirm the external signal changed, then enable monitoring where your plan supports it.

ExposureGrid continuously monitors these issues and alerts you before they become exploitable.

Run a private scan

Compare plans