DNS & domain lookup

DNS Propagation Checker

Check whether a DNS change has propagated by querying Cloudflare, Google, Quad9 and AdGuard at once and comparing answers. Free, live over DNS-over-HTTPS.

Check DNS propagation

Query several public resolvers at once and compare their answers.

What this propagation checker does

Queries Cloudflare, Google, Quad9 and AdGuard resolvers
Compares their answers to detect propagation
Supports A, AAAA, CNAME, MX, NS and TXT records
Highlights when resolvers disagree
Runs live over DNS-over-HTTPS
Shows each resolver's exact answer

Common use cases

  1. 1Confirming a DNS change has rolled out
  2. 2Checking after switching hosting or nameservers
  3. 3Verifying MX changes before cutover
  4. 4Diagnosing why some users see the old record
  5. 5Monitoring propagation during a migration
  6. 6Comparing answers across public resolvers

Related tools

DNS Record LookupA Record LookupNS Record LookupDNS Health CheckerWHOIS LookupNameserver migration checker

About DNS propagation

DNS propagation is the delay between changing a record and every resolver worldwide serving the new value. It happens because resolvers cache records for their TTL, so older answers linger until the cache expires.

This checker queries several major public resolvers at once and compares their answers. When they all agree, your change has effectively propagated; when they differ, some caches still hold the old record. Lowering the TTL before a planned change speeds this up.

More Free Tools Where This Came From

This utility is one of dozens of free, no-login tools for DNS, email, SEO and developers — all instant and private.

See All ToolsTalk to Our Team

HostCloud.in  ·  Pune, India  ·  Serving 34,987+ Websites Since 2020

FREQUENTLY ASKED QUESTIONS

Got Questions? We Have Answers.

What is DNS propagation?

It is the delay between changing a DNS record and every resolver worldwide serving the new value, caused by records being cached for their TTL.

How does this checker work?

It queries several major public resolvers (Cloudflare, Google, Quad9, AdGuard) at once and compares their answers. If they all agree, your change has effectively propagated.

Why do resolvers show different answers?

Some resolvers still hold the old record in cache until its TTL expires, so during propagation you may see a mix of old and new values.

How long does propagation take?

Usually minutes to a few hours, up to the record's TTL. Nameserver (NS) changes at the registry can take up to 48 hours.

How can I make changes propagate faster?

Lower the record's TTL a day before a planned change so caches expire sooner, then raise it again afterwards.

Is this a geographic check?

It compares major public resolvers rather than specific geographic locations, which is enough to confirm whether a change has rolled out.