No port could be tested
What this check looks for
We were not able to run the port check on ‹host›, so this section reports nothing at all rather than reporting that everything is closed.
Why it matters
A port check that did not run and a port check that found nothing open look identical unless one of them says so. Reporting an untested host as clean would be telling you a database is firewalled when nobody looked.
What it costs your score
This check never deducts. It reports a fact — or reports that something could not be verified — and is shown on the report without moving the score.
- Severity
- info
- Default confidence
- confirmed
- Status when triggered
- info
- Deduction
- 0 points
- Family cap
- none
- Category
- Network
- Module
- Net ports
- Fix owned by
- user
- In the ruleset since
- 2026.09
Technical detail
‹reason›
Port checks are TCP connections, and a Cloudflare Worker cannot make the ones this check needs — docs/22-infrastructure-decision.md §1.2 records the restriction, and §3.3 places net.ports on the external probe host for that reason and for the abuse posture the host provides. When that host is not configured, is unreachable, or refuses the target, this finding is the entire output of the module.
No exposure finding is emitted alongside it. Not a pass, not a fail, and not an empty list presented as a result. When the check runs, this section will list every port examined and its state.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.