Why has one resolver updated and another not?

Each caches independently, and each cache expires based on the TTL recorded when that resolver last queried — at a different moment. This is normal. Do not re-edit the record; simply wait out the longest TTL.

If all three agree, is the change complete?

It means these three common resolvers have updated, not that the world has. Corporate and carrier resolvers may apply their own caching policy and some ignore short TTLs. That is usually why some users still reach the old host.

NETWORK TOOLS · QUERIED BY OUR SERVER

DNS Propagation Checker

Query the same record from several public resolvers at once to see how far a DNS change has spread.

This lookup is made by our server contacting the host, not by your browser.

About this tool

The usual question after a DNS change is whether it has taken effect yet. This tool asks three public resolvers the same question and lists their answers side by side. If all three return the new value, the major public resolvers have updated. If one still returns the old value, its cache has not expired and you need to wait out the TTL. Treat this as a sample: there are tens of thousands of resolvers worldwide and this asks three common ones, so agreement is not proof of global completion — carrier-operated resolvers in particular often lag.

How it works

Enter a domain and choose the record type.
Compare what each resolver returns.
If a resolver still returns the old value, wait for the TTL to expire and check again.

Limits and notes

Queries Cloudflare (1.1.1.1), Google (8.8.8.8), and Quad9 (9.9.9.9). This is a sample, not a global survey: agreement here does not mean every resolver worldwide has updated.

How your input is handled

The domain or URL you enter is sent to our server, where an isolated process contacts the host on your behalf. Nothing you submit is stored or written to an analytics event, no cookies or authorization headers are forwarded, and the target's JavaScript is never executed. The server may only reach publicly routable internet addresses; private ranges, loopback, and cloud metadata addresses are refused.

Frequently asked questions

Why has one resolver updated and another not?: Each caches independently, and each cache expires based on the TTL recorded when that resolver last queried — at a different moment. This is normal. Do not re-edit the record; simply wait out the longest TTL.
If all three agree, is the change complete?: It means these three common resolvers have updated, not that the world has. Corporate and carrier resolvers may apply their own caching policy and some ignore short TTLs. That is usually why some users still reach the old host.

← All network tools