DNS Propagation
Compare DNS answers across public resolvers.
A DNS propagation checker queries public resolvers in several locations at once and shows the answer each one returns. When every resolver returns your new record the change has propagated; while some still return the old value, their cached copy simply has not expired yet.
Start a check
Public internet targets onlyResults
Ready when you are
Enter your details above and run the tool.
How DNS Propagation works
What it does
Compare DNS answers across public resolvers.
What you get
DNS answers, probe locations, TTL values and expected-value matches.
Live data sources
The target is sent to a network provider. Results include their source; timeouts and unavailable data are clearly marked.
What if a check cannot finish?
Confirm your input and try again. A timeout, blocked request, or unavailable provider is not proof that a domain is broken. Internet measurements and third-party services have limits.
DNS Propagation — frequently asked questions
How long does DNS propagation take?
Up to the TTL set on the record, and commonly 24–48 hours for nameserver changes because some ISP resolvers ignore short TTLs. A record with a 300-second TTL usually updates within minutes.
Why do some locations still show the old IP address?
Those resolvers are serving a cached answer that has not reached its TTL yet. Nothing is wrong — they refresh on their own. Clearing your own device's cache has no effect on them.
Can I force DNS to propagate faster?
No. You can only lower the TTL before making a change so caches expire sooner afterwards. Once an answer is cached, its TTL has to run out.