Why does "Origin server exposed" 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.

Origin server exposed: what it means, why it may matter, and how to remediate with external verification using ExposureGrid.

Origin server exposed: Origin/CDN/WAF topology mistakes can let traffic bypass intended protections or reveal infrastructure.

Direct-origin access can weaken DDoS/WAF value and leak operational context - severity depends on hardening at origin.

Map DNS to edges vs origin, verify firewall allowlists, test direct-origin reachability hypothesis carefully.

Firewall origin to edge IP ranges, avoid leaking origin via DNS/certs, validate coverage on apex/www/subs.

Run a scan to verify this fix on your domain

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

ExposureGrid compares edge vs origin signals where configured for your plan.

Why does "Origin server exposed" 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