Why does "Http Probe Blocked" 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.

Http Probe Blocked: what it means, why it may matter, and how to remediate with external verification using ExposureGrid.

Http Probe Blocked: Scans may be blocked, partial, or inconclusive - a coverage limitation is not the same as a clean bill of health.

False reassurance is harmful; rerun or widen verified coverage before assuming posture.

Retry scans, validate network blocks, supply route lists where scanners support options, attach verified domains for deeper analysis.

Ensure edges allow scanners as policy permits; fix connectivity; treat partial results as unanswered questions.

Run a scan to verify this fix on your domain

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

ExposureGrid records probe failures and partial coverage explicitly when observed.

Why does "Http Probe Blocked" 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