DNS Propagation Checker

Compare DNS records across six public resolvers, check expected values and remaining TTL, and monitor changes with optional repeat checks.

Runs in your browser

Six public resolvers, not every ISP cache. Optional Google ECS diagnostics are not remote probes and may be ignored; they do not count toward the match percentage.

One record per line; keep MX priority and host together. TXT is case-sensitive.

Optional Google ECS diagnostics

Your browser sends the domain and your public IP to six public DNS resolvers. Optional ECS requests go to Google with the displayed subnet. Requests begin only when you press Check resolvers.

Repeat checks stop at 100%, 60 rounds, 30 minutes or when this tab becomes hidden.

These six resolvers do not represent every country or ISP cache. ECS diagnostics are Google requests, not remote probes; the server may ignore the subnet. They are excluded from the match percentage to avoid counting Google repeatedly.

What the match percentage means

A match means the complete returned record set equals your expected set, or the most common set if no expected value is supplied. Failed requests are excluded from the denominator and listed separately. This is a comparison of six resolvers, not proof of global completion.

TTL is an estimate, not a deadline

The largest remaining TTL among differing answers estimates how long the observed caches may keep them. Negative caching, stale-answer policies and authoritative-server changes can extend what users see. A zero TTL is not a guarantee of immediate propagation.

Expected values and record sets

Enter each MX record with its numeric priority and host on the same line. TXT values retain case and internal spaces. IPv6 notation is normalized, duplicate records are removed and ordering does not affect equality.

Why Google ECS is separate

ECS adds a client-subnet hint to a Google query; it is not a request from that country’s ISP. A returned scope of /0 reports no regional distinction. Counting repeated Google queries as independent locations would distort agreement, so diagnostics are excluded from the percentage.

Bounded monitoring

Repeat checks are opt-in and are never enabled by a shared URL. Monitoring stops at 100% agreement, 60 rounds, 30 minutes or when the tab becomes hidden. History remains in memory and disappears on reload.

How to use

  1. Enter the domain and choose the record type.
  2. Optionally enter the new values you expect, one record per line.
  3. Press Check resolvers and compare answers and remaining TTLs.
  4. Enable repeat checks if needed; Stop cancels pending requests.

FAQ

Does 100% mean DNS has updated everywhere?

No. It means the successful selected resolver responses match. Failed resolvers and other ISP caches remain unverified.

Can I monitor automatically?

Choose a 15, 30 or 60 second interval before starting. Monitoring is bounded and stops when the tab is hidden.

Why is there no world map?

These requests come from your browser, not probes deployed around the world. Resolver brands and optional subnet hints are shown directly.

Is the TTL estimate guaranteed?

No. It describes observed cache lifetimes, not every resolver or future authoritative answer.

Related tools

More Internet tools: Internet

Send feedback

Found a bug or have an idea? Tell us — it helps make the tools better.

Only needed if you would like a reply.

Page: /internet/dns-propagation-checker/