Protocol and cipher support could not be tested
What this check looks for
We could not run the handshakes needed to find out which TLS versions this server accepts, so this part of the report is missing rather than clear.
Why it matters
An untested check is not a passing check. This is here so an outage on our side never reads as good news about your server — nothing below is an assurance that legacy protocols are disabled.
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
- TLS
- Module
- Tls protocols
- Fix owned by
- third party
- In the ruleset since
- 2026.09
Technical detail
‹reason›
Enumerating protocol versions requires a handshake per version with a ClientHello we control, and on this run those handshakes could not be made, so the check is reported as not run rather than as clean. Re-running the scan later will complete it.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.