01A simple answer before the DNS jargon
DNSReach starts with what matters: do the usable DNS services agree, is the expected value visible, and is there anything you should investigate?
Open technical details when you need resolver names, TTLs, timings, response codes and endpoint-level evidence.
Example18 of 18 responding services agree.
One service could not be reached. Your DNS answer itself is consistent.
02Resolver comparison without false voting
A resolver provider may have several IPv4 and IPv6 endpoints. DNSReach can test those endpoints for reachability and consistency, but the provider counts once in resolver consensus.
Useful for
Propagation checks, cache differences, ISP resolver problems and support evidence.
03Real geographic checks
Connected DNSReach nodes make DNS queries from their actual locations. This is different from asking a global anycast resolver and guessing where the query ran.
Kept separate
Geographic nodes, fixed-location resolvers and global anycast networks are labelled differently so the map does not imply evidence that does not exist.
04Authoritative DNS comparison
DNSReach checks the nameservers responsible for the DNS zone and compares their answers with recursive resolver caches. This helps show whether the source is correct while caches are still changing.
Technical view
See each authoritative server, returned value, response state and direct comparison.
05Propagation tracking
Tell DNSReach the new value you expect. It shows which comparable sources already return it and which still have another valid answer.
No false errors
A different valid answer, timeout, refusal and DNS error are different things. DNSReach reports them separately.
06Share, export and connect
Use result links and exports for support work. Higher plans can add programmatic access through the API and MCP services as those capabilities are enabled.
For technical teams
Structured data makes the same DNS evidence useful in tools, workflows and automation.