Skip to content

DNS Propagation Checker

Ask 8 public DNS resolvers at once and see whether your DNS change has reached them.

This tool runs on our server, because a browser cannot send DNS queries, pings or raw network connections. Only the domain, address or URL you enter is sent; results are not stored. Privacy

Asks 8 public DNS resolvers around the world at once and compares their answers.

Report a problem

Don't include personal or sensitive information.

What happened, and what did you expect? (10–2000 characters) 0 / 2000

Your browser and system, screen size and recent error messages on this page. Never what you typed or your files. Privacy

What is sent
 

Changed an A record, moved your site to a new host or switched name servers? DNS changes do not reach everyone at once, because resolvers cache the old answer until its TTL expires. This tool asks eight large public resolvers – Cloudflare, Google, Quad9, OpenDNS, AdGuard, Control D, CleanBrowsing and Yandex – at the same moment and shows their answers side by side.

Rows that match the most common answer get a ✅, and rows that still differ get a ⚠️, together with the remaining TTL and the response time. When every resolver agrees, the change has propagated to these networks, and most visitors will see the new record.

How to use the DNS Propagation Checker tool

  1. Enter the domain or subdomain you changed, for example www.example.com.
  2. Pick the record type you edited (A, AAAA, CNAME, MX, NS, TXT …).
  3. Click Check propagation.
  4. Compare the answers. Check again after the TTL shown has passed for resolvers that still show the old value.

Why use ToolOrca DNS Propagation Checker

  • 8 major public DNS resolvers queried in parallel
  • Highlights answers that differ from the majority
  • Remaining TTL per resolver, so you know how long to wait
  • All common record types, including MX, NS, TXT and CAA
  • Results in about a second, shareable by link

How long does DNS propagation take?

It depends on the TTL of the old record. A resolver that cached a record with a TTL of 3600 seconds may keep it for up to an hour after you change it. Name server (NS) changes at the registrar can take longer – often up to 24–48 hours – because the parent zone's NS records usually have long TTLs.

To make a planned move fast, lower the TTL to 300 seconds a day before the change, make the change, check here, and raise the TTL again once everything is stable.

Different answers that are not a problem

CDNs and large websites (Google, Cloudflare, Akamai, AWS CloudFront) return different IP addresses from different resolvers on purpose, so each visitor reaches a nearby server. If the addresses differ but all belong to your CDN, propagation is fine.

For a single server, every resolver should eventually show the same address. If one keeps an old value long after the TTL, the record may still exist at your old DNS host – check which name servers the domain really uses with a DNS lookup of the NS records.

Frequently asked questions

Why does my old website still show after changing DNS?

Your own computer and router cache DNS too. Flush the cache (or wait for the TTL) and try a private browser window.

Which resolvers are checked?

Cloudflare 1.1.1.1, Google 8.8.8.8, Quad9 9.9.9.9, OpenDNS, AdGuard DNS, Control D, CleanBrowsing and Yandex DNS.

Can I force propagation to go faster?

Not for other people's resolvers. Cloudflare and Google offer pages to purge their cache for a name; otherwise wait for the TTL.

Does this check name server changes?

Yes. Choose the NS type to see which name servers each resolver currently returns for the domain.

Can I check a device on my home or office network?

No. For safety, private and local addresses (192.168.x.x, 10.x.x.x, localhost, .local names and similar) are refused. Our server can only test public hosts on the internet.