Some resolvers did not answer and were not counted
What this check looks for
Some of the public resolvers we ask did not reply. They are excluded from the comparison rather than counted as disagreeing, because a resolver that said nothing has told us nothing.
Why it matters
Counting a silent resolver as a disagreement would turn one operator's outage into a finding about your domain. Listing them separately is how the agreement figure above stays meaningful.
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
These resolvers produced no usable answer: ‹resolver list›. A SERVFAIL, a REFUSED, a timeout or a transport error is a failure to observe, not an observation of a different value, so none of them votes in the consistency verdict. A SERVFAIL from a validating resolver is the exception worth following up: it can indicate a DNSSEC validation failure, which the DNSSEC section reports separately.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.