Global DNS Propagation Checker — IT Ops Tools

Try:

How this works

Your check runs on our server, which sends a DNS query directly to each resolver over UDP port 53. Each resolver answers from its own cache, so right after a change some locations show the new value while others still serve the old one until their TTL expires. A green check means the location agrees with the majority answer; amber means it still differs; grey means no response.

Resolvers shown as Global are anycast (Google, Cloudflare, Quad9, OpenDNS…): the same IP is announced worldwide, so their answer reflects the node nearest our server rather than a specific country. Resolvers pinned to a country are physically fixed there and give a true geographic signal — most useful for spotting GeoDNS/CDN differences and regional propagation lag.

Each check samples a rotating set of resolvers from a large global pool — a curated set of well-known resolvers plus a daily-refreshed list of public resolvers from public-dns.info — so running the check again queries a different set of locations and widens coverage over repeated checks.

What PropCheck checks

A server-side resolver-sampling pipeline — your check queries DNS resolvers worldwide directly over UDP port 53.

Worldwide Resolver Sampling

Queries a rotating set of resolvers from a large global pool, mixing well-known public resolvers with a daily-refreshed list of resolvers from public-dns.info, spanning continents and providers.

Live Propagation Map

Plots each resolver's answer on a world map in real time — agreeing locations show green, divergent locations show amber, and unresponsive ones show grey, so you can watch a change roll out.

Seven Record Types

Checks A, AAAA, CNAME, MX, NS, TXT and SOA records — covering the most common DNS change scenarios, from A/AAAA cutovers to MX migrations and TXT-based verification records.

Anycast vs. Geographic Resolvers

Distinguishes anycast resolvers (Google, Cloudflare, Quad9, OpenDNS) — whose answer reflects the node nearest our server — from resolvers physically pinned to a country, which give a true regional signal for spotting GeoDNS/CDN differences.

Filter & Compare Settings

Hide resolvers with no answer or show only the locations that differ from the majority — useful for quickly isolating the handful of resolvers still serving a stale TTL.

Direct UDP/53 Queries

Each check runs server-side, querying resolvers directly over UDP port 53 — no third-party propagation API in the middle, so results reflect what each resolver actually has cached right now.

Frequently asked questions

What is DNS propagation?

DNS propagation is the time it takes for a DNS change to be visible everywhere. Resolvers around the world cache records until their TTL expires, so after an update some locations return the new value while others still serve the old one.

How long does DNS propagation take?

Usually anywhere from a few minutes to 48 hours. The main factor is the record TTL: a resolver keeps serving its cached answer until the TTL counts down, so records with lower TTLs propagate faster.

Why do some locations still show the old DNS record?

Those resolvers cached the previous answer and will not refetch until the TTL expires. Anycast resolvers and ISPs that stretch short TTLs can also lag, which is why a change can look complete in one region but not another.

How do I check if my DNS has propagated globally?

Enter your domain, pick the record type (A, AAAA, CNAME, MX, NS, TXT or SOA) and run the check. PropCheck queries resolvers worldwide and shows, on a live map, how many agree with the majority answer.

Is PropCheck free?

Yes. PropCheck is free, needs no account, and queries resolvers directly server-side over UDP port 53 — there is no third-party propagation API in the middle.