DNS Propagation Checker

Check DNS propagation across multiple global DNS servers. Queries Google, Cloudflare, OpenDNS, Quad9, and more.

DNS propagation is the time it takes for DNS changes (new records, updated IPs, name server changes) to spread across the internet. When you update a DNS record, it doesn't take effect everywhere instantly — different DNS servers around the world need time to refresh their caches.

Use this tool to verify DNS changes after migration, check if new records are live everywhere, troubleshoot mixed results across locations, and understand your domain's TTL (Time To Live) settings. Propagation typically takes 0-48 hours depending on TTL values.

This DNS propagation checker queries these public resolvers:

Google Public DNS — 8.8.8.8, 8.8.4.4
Cloudflare DNS — 1.1.1.1, 1.0.0.1
Quad9 — 9.9.9.9
OpenDNS — 208.67.222.222

Domain

Record Type

Examples:

Want the full picture?

Run a free Website Health Check →

Common questions

What is a DNS propagation checker?

It queries several public DNS resolvers for the same name and record type so you can see whether a change has reached Google, Cloudflare, Quad9, and OpenDNS yet — not just your laptop's cache.

What is DNS propagation?

DNS propagation is the time it takes for DNS record changes to spread across resolvers worldwide, typically minutes to 48 hours depending on TTL.

Which DNS servers does this checker query?

Google Public DNS (8.8.8.8 and 8.8.4.4), Cloudflare (1.1.1.1 and 1.0.0.1), Quad9 (9.9.9.9), and OpenDNS (208.67.222.222). We cannot query every ISP cache on Earth.

Can I force DNS propagation to speed up?

You cannot force propagation globally, but you can lower your TTL 24–48 hours before making changes and flush your local DNS cache to see updates sooner.

What DNS propagation checking shows

After you change an A, AAAA, MX, CNAME, or TXT record, resolvers worldwide do not update instantly. Each recursive resolver caches answers until the record’s TTL expires. This tool queries multiple public resolvers and compares what they return for the same name and record type, so you can see whether a change has reached major networks yet.

When to check propagation

After pointing a domain to a new host or CDN
After switching email providers (MX / SPF / DKIM TXT)
When some users see the new site and others still see the old one
Before declaring a migration “done” and shutting down the old server

How to read the results

Consistent answers across resolvers mean the change has largely propagated. Mixed IPs or MX targets usually mean some caches still hold the previous value. Empty or SERVFAIL responses can mean the zone is mis-delegated, the TTL has not cleared, or the nameserver is unreachable from that resolver’s network. Always compare against the value your DNS panel shows as authoritative.

Common mistakes

Expecting global updates in minutes when TTL is still 24 hours
Changing records at the registrar while NS still point elsewhere
Testing only from your laptop (one recursive cache) and assuming the world matches
Lowering TTL after the cutover instead of 24–48 hours before

Example scenario

A storefront cut over to a new VPS but half of customers still hit the old IP. Propagation checks showed Cloudflare and Google resolvers already returned the new A record, while a regional ISP still served the previous address. Waiting out the remaining TTL — then flushing the ISP cache — resolved the split view without rolling back DNS.

Limitations

We sample a set of public resolvers; we cannot query every ISP cache on Earth. Local browser or OS DNS caches can still show stale data after public resolvers agree. For a single authoritative answer, use DNS Lookup.

Related resources

How DNS Propagation Works · DNS Lookup · DNS, Email & SSL Checklist · Website Health Check