Saltar al contenido
Network troubleshooting

DNS Propagation Checker

Has your DNS change reached the world yet? Compare the answer from the domain’s own nameservers with Google, Cloudflare, Quad9, OpenDNS and other public resolvers.

Live test from our server in Australia – nothing is stored.

After changing a DNS record or moving a domain to new nameservers, some visitors see the new server and some the old one until every resolver’s cache expires. This checker asks the domain’s own nameservers for the true answer and compares it with what Google, Cloudflare, Quad9, OpenDNS and other public resolvers around the world return right now.

How to use it

  1. Enter the exact name you changed – example.com and www.example.com are separate records.
  2. Choose the record type: A for websites, MX for mail, TXT for SPF/DMARC/verification, NS after a nameserver change.
  3. Rows marked Different still hold the old answer; they update when its TTL runs out.

Speeding things up

  • Lower the TTL to 300 seconds a day before a planned change.
  • Most public resolvers let you flush a name: Google (dns.google/cache) and Cloudflare (one.one.one.one/purge-cache).
  • Flush your own PC’s cache with ipconfig /flushdns (Windows) or sudo resolvectl flush-caches (Ubuntu).

Preguntas frecuentes

How long does DNS propagation take?

A changed record is fully visible once every resolver’s cached copy expires – up to the old record’s TTL (often 1–4 hours). Changing nameservers at the registrar can take up to 48 hours because the parent zone’s NS records have long TTLs.

How can I make the next change faster?

A day before the change, lower the record’s TTL to 300 seconds. After the change has settled, raise it again.