DNS Propagation Emulator
When a DNS record changes, each resolver keeps serving its cached copy until the record's TTL expires, so different regions switch at different times. This page models that cache behaviour from the TTL and elapsed time — it does not query live resolvers.
Why propagation is not instant
A resolver caches an answer for the TTL set by the authoritative server. If a resolver fetched the record just before your change, it may hold the old value for almost the full TTL; if it fetched earlier, it flips sooner. That is why a 24-hour TTL can mean a day of mixed answers.
Lower the TTL a day before a planned migration, make the change, then raise it again. Real resolvers may also ignore TTLs or use forwarders, so confirm with live DNS lookups from several regions.
This tool runs entirely in your browser. Your inputs and files are processed locally and are never sent to or stored on Kinetikatech servers.
Related pages
Server problem? Hacked site? Slow website?
Critical issues answered within 30 minutes, 24 hours a day, 7 days a week.