Does DNSReach count every resolver IP separately?
No. Multiple IPv4 or IPv6 endpoints can belong to one logical resolver. That resolver counts once in consensus.
Short answers to the questions that come up most often.
No. Multiple IPv4 or IPv6 endpoints can belong to one logical resolver. That resolver counts once in consensus.
No. Anycast and public resolvers are not presented as if they prove a query came from one city. DNSReach geographic nodes are separate.
It lets DNSReach compare answers with the DNS value you expect during a change and report propagation progress.
No. A timeout means that source did not answer in time. It is kept separate from a valid DNS answer that differs.
Yes. PTR checks accept IPv4 and IPv6 addresses.
DNS caches refresh at different times. DNSReach separates a different valid answer from a timeout, refusal or DNS error so you can see what is actually happening.
These are the nameservers responsible for the DNS zone. DNSReach checks them separately so their answers do not distort public resolver consensus.
DNSReach nodes run checks from real installed locations. They are shown separately from global anycast resolvers because the two types of evidence answer different questions.
DNSSEC evidence is being expanded. Where DNSSEC information is available, DNSReach keeps validation evidence separate from ordinary record comparison.
Eligible accounts can use authorised API or MCP access. Scraping the public website or bypassing plan limits is not permitted.
DNSReach can hold an unhealthy endpoint out of public comparison while continuing health tests. Healthy endpoints for the same logical resolver can continue to work.
Run a check first, or contact technical support if you need help understanding the evidence.