KitJade
Network & CybersecurityPublic lookupNew

DNS Propagation Checker

Compare answers from two independent public resolvers.

Use the DNS Propagation Checker tool

Calls public DNS / lookup servicesUpdated Report a problem

What this dns propagation checker does

After a DNS change, cached answers can persist until their TTL expires. This checker queries the same record through Cloudflare and Google public resolvers and shows each answer set, plus whether the two agree.

Two resolvers are not the whole world. The result tells you whether two large, independent caches have picked up the change; a resolver elsewhere may still serve an older answer until its own TTL runs out.

Why use it

  • Check whether a recent DNS edit has reached public caches.
  • Compare TTLs before changing a record again.
  • See whether two networks see the same address for a hostname.

How to use it

  1. 1Enter the domain and choose a record type.
  2. 2Run the comparison.
  3. 3Read both answer sets and the agreement notice.

Worked examples

Matching A records

Input

example.com, type A

Output

Both resolvers return the same addresses and a similar TTL.

Mismatch

Input

A record changed minutes ago

Output

One resolver still serves the old address; wait for the TTL or query the authoritative server.

Common mistakes

  • Expecting instant propagation; DNS is cached by design and TTL governs how long.
  • Changing a record repeatedly while old caches still hold previous values.
  • Checking a subdomain when the record was published at the apex.

Frequently asked questions

How long does propagation take?
It depends on the previous record's TTL and how long resolvers keep entries. Lower the TTL before a planned change to shorten the window.
Why do the two resolvers disagree?
They cached the answer at different times, or the authoritative servers are inconsistent. Check the TTLs and query the authoritative nameservers directly.
Does this check every country?
No. It compares two public resolvers. Global propagation is a distributed cache problem, not a single switch.
All tools