DNS propagation check
Changed a DNS record and want to know if the world can see it yet? This asks the major public DNS services the same question and shows whether they agree. Each service keeps its own cached copy until the record's TTL runs out, which is why a change can show up in some places before others.
| DNS service | Based in | Answer | Cached for | Reply |
|---|
Why DNS changes take time
Nothing actually travels across the internet when you change a record. Every DNS service keeps its own copy of an answer for as long as the record's TTL allows, and only asks again when that runs out. Until then it keeps handing out the old answer. So a record with a one-hour TTL can take up to an hour to change everywhere, and a change of name servers at a registrar can take a day or two, because those records are usually cached for much longer.
How to make a change take effect faster
Lower the TTL a day or two before the change, to something like 300 seconds. Once the old, long TTL has expired everywhere, the switch itself is seen within minutes. Raise the TTL again afterwards.
What this check covers
It asks eight large public DNS services, from a server near you, and compares their answers. It cannot see inside your own internet provider's DNS or your computer's cache. If the services here agree but your browser still shows the old site, restart the browser or clear your device's DNS cache.