The delegation could not be checked
Updated
What this check looks for
We could not reach your nameservers directly, so none of the delegation checks ran. This says nothing about your zone — only that we could not look.
Why it matters
A checker that shows nothing and a checker that shows nothing wrong look identical unless it says which one happened. This finding exists so they never can be confused.
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
- DNS
- Module
- Dns health
- Fix owned by
- user
- In the ruleset since
- 2026.09
Technical detail
‹reason›
Checking a delegation means asking the parent zone which nameservers it hands your domain to, then asking each of those nameservers directly whether it actually answers for the domain. This scan could not follow that path, so none of the checks below ran.
Every one of them is reported as not tested rather than assumed to pass: a lame nameserver, a mismatch between what the parent publishes and what your zone publishes, or missing glue would all look exactly like this. Run the scan again; if it keeps saying this, the shortfall is ours and not your domain’s.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.