Has this DNS change spread yet?
Asks five public resolvers for the same record and compares their answers. It shows whether they agree — not whether the record is the one you meant to publish.
Example result
A records for example-company.com
These resolvers are not returning the same A answer. There are two ordinary reasons for that, and this tool cannot tell them apart. Either a recent change is still spreading — each resolver serves its cached copy until that copy expires, and the record's TTL is what governs how long that takes — or the domain answers differently on purpose, which is how round-robin and geographically balanced DNS work. Compare the answers below: a change part-way through looks like some resolvers on the old value and some on the new, while deliberate balancing looks like scattered answers from the same pool.
Queried 5 public resolversCloudflare
Cloudflare (1.1.1.1) returned this answer, matching Google and Quad9 but not the rest.
203.0.113.42Google (8.8.8.8) returned this answer, matching Cloudflare and Quad9 but not the rest.
203.0.113.42Quad9
Quad9 (9.9.9.9) returned this answer, matching Cloudflare and Google but not the rest.
203.0.113.42OpenDNS
OpenDNS (208.67.222.222) returned this answer, matching Level3 but not the rest.
198.51.100.7Level3
Level3 (4.2.2.1) returned this answer, matching OpenDNS but not the rest.
198.51.100.7Example result · five public resolvers · nothing stored · no account