All free tools

DNS propagation checker

Changed a DNS record and not sure it is live yet? Compare the answer from three large public resolvers, and optionally the value you expect to see.

Guides that use this tool

How to use it

  1. Enter the domain or host name you changed, for example www.contoso.com.
  2. Choose the record type, and if you like, paste the new value you expect (an IP address, a CNAME target or part of a TXT record).
  3. Each resolver shows its answer and TTL. Green means it matches the others, or the value you expect.

Why changes take time

DNS has no push mechanism. Every resolver keeps the old answer until the record’s TTL expires, then asks your DNS host again. Lower the TTL (for example to 300 seconds) a day before a planned change, and the switch-over is quick.

Related guides

Questions people ask

How long does DNS propagation take?

As long as the old record’s TTL, plus a little. With a TTL of 3600 seconds most resolvers update within an hour. Name server changes at the registrar can take up to 48 hours because the TLD caches NS records for longer.

Why do resolvers show different answers?

Either some still have the old record cached, or your DNS host returns different answers by location (geo DNS or a CDN). If the difference lasts longer than the TTL, check the record at your DNS host.

Which resolvers does the tool use?

Cloudflare (1.1.1.1), Google Public DNS (8.8.8.8) and AliDNS (223.5.5.5), queried over DNS-over-HTTPS from your browser.

Can I flush the cache of a public resolver?

Cloudflare and Google both offer a purge page for their public resolvers (1.1.1.1/purge-cache and developers.google.com/speed/public-dns/cache). Your own computer also caches DNS: run ipconfig /flushdns on Windows.