Check whether a DNS change has propagated across major public resolvers.
Every other tool on this site runs entirely as JavaScript in your browser and never contacts a server at all. This one is a deliberate exception, by necessity: the domain you enter is sent to this site’s server to run DNS queries against several public resolvers — unavoidable, since browsers can’t query DNS directly — nothing about the lookup is logged. Nothing about the request is logged, stored, written to a cookie, or shared with any third party — it's handled and discarded the moment the response is sent back to you.
This describes only what this specific tool does with what you type into it. It doesn't cover the rest of this site — see the Privacy Policy for how analytics and advertising cookies are handled elsewhere.
DNS changes don't take effect everywhere instantly — different resolvers around the world cache records for different lengths of time (controlled by the record's TTL), so right after you change a DNS record, some resolvers may still be serving the old value while others already show the new one.
This tool queries the same record directly against four major public DNS resolvers — Google, Cloudflare, Quad9, and OpenDNS — so you can see at a glance whether your change has reached all of them yet, rather than guessing based on what your own machine happens to show (which only reflects whichever single resolver you're configured to use).
If some resolvers still show the old value, that's expected and usually just a matter of waiting out the previous record's TTL — it's not a sign anything is broken, and there's no way to force propagation faster than that cached TTL allows.
Each resolver independently caches DNS answers for as long as the record’s TTL says to. A resolver that cached the old value 5 minutes before your change won’t see the new one until that cached entry expires — this is normal, expected behavior, not a problem.
It depends entirely on the TTL your previous record was set with — anywhere from a few minutes to 24-48 hours for a record that had a long TTL. There’s no way to speed this up retroactively once the old record was already cached somewhere.
Lower the TTL on a record well before you plan to change it (a day or more ahead), so by the time you actually make the change, resolvers are already caching it for a much shorter window.