DNS Propagation Checker
Check whether your DNS changes are already visible on the world's major public resolvers.
When you change a DNS record (for example when migrating servers or setting up a new domain), the change is not instant: each resolver keeps its own cache and respects the record's TTL. This tool queries several of the most-used public DNS resolvers in parallel and shows you what value each one returns, so you know whether propagation has finished.
We query the major public DNS resolvers live via DNS-over-HTTPS from your browser.
DNS propagation FAQ
It depends on the record's TTL. It usually takes anywhere from a few minutes to 48 hours. Resolvers cache the answer for the time set by the TTL, so a low TTL (300s) propagates faster than a high one (86400s).
Because each resolver has its own independent cache that expired at a different moment. This is completely normal during propagation: when they all agree, the change has finished propagating.
Lower the record's TTL to 300 seconds a few hours BEFORE making the change. That way, when you update the value, caches will expire sooner. There's no way to force third-party resolver caches to flush.
It queries, live, the major anycast public resolvers with a global footprint and different regional views (Cloudflare, Google in the US, DNS.SB in Europe and AliDNS in Asia). It reflects what most real Internet users see. These are the only ones that allow secure DNS-over-HTTPS queries directly from the browser.
Ready to improve your DNS?
Choose the best free DNS server for your needs and configure it in minutes.