DNS Propagation Checker

Check whether your DNS change has reached the public resolvers of Google, Cloudflare and Quad9.

Queries the public DNS over HTTPS (DoH) resolvers of Google, Cloudflare and Quad9.

Check DNS propagation for any record

Changed a DNS record and want to know if it is live? Enter your domain, pick a record type and press Check Propagation. The checker asks the public DNS over HTTPS resolvers of Google, Cloudflare and Quad9 for the record and lists what each one returns. You can check A, AAAA, MX, TXT, CNAME, NS, SOA and PTR records.

When all three resolvers return the same value, the checker reports that the records are consistent. When the answers differ, the change is still spreading or an old copy is cached on one of them.

How to check DNS propagation

  1. Enter your domain name, for example example.com. A subdomain such as mail.example.com works too.
  2. Choose the record type you changed.
  3. Press Check Propagation.
  4. Compare the value from each resolver with the value you set at your DNS provider.

How to read the results

  • Same value on every resolver: the change has reached all three.
  • Old value on some resolvers: those resolvers still hold the previous record in their cache and refresh it when the TTL runs out.
  • No records of this type: the resolver answered, but it has no record of the type you selected.
  • Domain not found (NXDOMAIN): the resolver says the domain does not exist. For a new domain or a nameserver change, it may not have picked up the update yet.
  • Error: a resolver did not answer. Run the check again after a moment.

Google, Cloudflare and Quad9 are large public resolvers. Your visitors may use others, such as the resolver of their internet provider. A match on all three is a good sign, but visitors on other resolvers can still see old data until their cache expires.

How long does DNS propagation take?

It can take from a few minutes up to 48 hours. The main factor is the TTL (time to live) of the old record, which tells resolvers how long they may keep a cached copy. A record with a TTL of 3600 seconds can stay cached for up to an hour after you change it. Nameserver changes are usually the slowest.

Other factors that affect the wait:

  • Record type: A, AAAA, MX, TXT and CNAME records follow the TTL you set. NS changes depend on your registrar and the parent zone.
  • Resolver cache: each resolver refreshes on its own schedule.
  • Your DNS provider: some providers publish changes to their servers faster than others.

Tips to speed up DNS propagation

  • Lower the TTL ahead of time: set a short TTL a day before the change so old copies expire quickly.
  • Wait out the old TTL: resolvers keep the previous record until it ends.
  • Flush your own DNS cache after the change, so your device asks for the new record:
    • Windows: ipconfig /flushdns
    • macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
    • Linux with systemd: resolvectl flush-caches

Once your records match, run a DNS leak test to see which DNS servers your own connection uses and look up the owner of an address with our IP WHOIS Lookup. If a site still will not open after a DNS change, our website status checker shows whether it is down for everyone and how fast it answers from several regions.

Frequently asked questions

How do I check if DNS has propagated?
Enter the domain and record type above and press Check Propagation. If Google, Cloudflare and Quad9 all return your new value, the change has propagated to those resolvers.
Why do the resolvers show different results?
Each resolver keeps its own cache and refreshes a record only after its TTL ends. During a change, some resolvers return the new value while others still return the old one.
Can I check MX, TXT and CNAME propagation?
Yes. Select the record type before you press the button. The checker supports A, AAAA, MX, TXT, CNAME, NS, SOA and PTR records.
Why does my DNS provider show the new record while the checker shows the old one?
Your provider's panel shows what it has saved on its own servers. The checker shows what public resolvers return, and those can still hold a cached copy of the old record until the TTL ends.
Is a DNS propagation check the same as a DNS leak test?
No. A propagation check tells you whether a change to your domain's records has spread. A DNS leak test tells you which DNS servers your own connection uses.

For more on related topics, explore our other resources: