How to use it
- 1
Enter a domain without protocol or path.
- 2
Choose A, AAAA, CNAME, MX, NS, or TXT.
- 3
Compare answer sets, partial errors, and TTLs.
What the tool can do
- Queries four fixed public recursive resolvers in parallel.
- Compares values and MX priority while ignoring TTL differences.
- Shows backend-to-resolver latency as a diagnostic signal.
Common use cases
- Compare cache state after a DNS change.
- Find resolver-specific mismatches or partial timeouts.
- Check one record type without a full zone audit.
How it works inside
Resolver snapshots depend on TTL, recursive cache, and request time.
Authoritative nameservers should be checked for final verification.
Questions and answers
Why do answers differ?
TTL, different cache states, geo-aware DNS, or a zone error can cause differences; the tool does not guess the cause automatically.
Do four matching answers prove full propagation?
No. It is only a consistent snapshot of the selected resolvers from the WebDiag backend.
