No resolver could be asked what it is serving
What this check looks for
We could not query the public resolvers, so nothing was compared. This says nothing about your domain — only that the check did not run.
Why it matters
A blank propagation table has to be distinguishable from a consistent one, or the report would be reassuring you on the strength of having looked at nothing.
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 propagation
- Fix owned by
- user
- In the ruleset since
- 2026.09
Technical detail
‹reason›
This check asks a dozen public resolvers around the world the same question and compares their answers, which is how a half-finished record change shows up: some of the internet sees the new value and some still sees the old one. This scan could not ask them, so nothing about agreement between resolvers is reported.
No finding here says your records agree. If you have just changed a record, check again shortly.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.