No port could be tested
Updated
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›
Checking which ports a host has open means opening a connection to each of them in turn. This scan could not, so no port was tried and none is reported.
That is not the same as a clean result, and this section is careful not to look like one: no port list, no pass, no fail, and no empty table presented as an answer. A database or an admin panel listening where it should not be would be invisible here. When the check does run, this section lists every port it examined and what it found on each.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.