Free checker - no signup required

Free DNS Propagation Checker

Check whether a DNS change has propagated by querying multiple public resolvers worldwide at once and comparing the answer each one returns for A, AAAA, MX, TXT, NS, or CNAME.

Run the check

Enter a domain to check it live against the IntoDNS.ai engine. No signup, no rate-limited trial.

What this DNS propagation checker verifies

When you change a DNS record, the new value does not appear everywhere at once. This tool queries the record you select — A, AAAA, MX, TXT, NS, or CNAME — across a set of independent public resolvers and shows, side by side, exactly what value each one is currently returning. For every resolver it reports the location and operator, the value(s) it resolved, and whether the query succeeded. It then compares all the answers and tells you whether they agree (propagation is consistent) or still differ (the change is mid-flight), along with the percentage of resolvers that have the record and the average response time.

What DNS propagation actually is

There is no global push that updates DNS everywhere when you edit a record. What people call propagation is really cache expiry. Each resolver that previously looked up your record cached the answer for the duration of its TTL (time to live). Until that cached copy expires, the resolver keeps serving the old value; only after expiry does it ask your authoritative nameservers again and pick up the new one. So "waiting for propagation" is waiting for the longest relevant TTL to lapse across all the resolvers your users hit. That is why two people in different places can see different answers for the same name at the same moment — and why this checker queries many resolvers rather than just one.

How TTL controls propagation speed

The single biggest lever on propagation time is the TTL you set before you make a change. If a record has a TTL of 3600 seconds, a resolver that cached it can keep serving the old value for up to an hour after you update it. The professional move is to lower the TTL (to, say, 300 seconds) a day or two ahead of a planned change, let the old high TTL expire everywhere, make the change while the TTL is low so it spreads within minutes, then raise the TTL back up once you have confirmed the new value. This checker is how you confirm: when every resolver row shows the new value, the change has propagated as far as public DNS can show you.

How to read the result

If every resolver returns the same value, the change is consistent and effectively propagated. If some resolvers still show the old value while others show the new one, you are watching propagation happen in real time — the inconsistency note lists the competing values and how many resolvers hold each. A resolver that fails to answer is usually a transient timeout rather than a real problem. Note one nuance: a "fully propagated" result across these public resolvers does not guarantee a specific end-user's ISP resolver or their device has refreshed yet, because those have their own caches this tool cannot see. It is a strong, representative signal, not an absolute guarantee for every machine on earth.

Propagation is not a fix for a broken record

A common trap is to blame "propagation" for a record that is simply wrong or missing. If this checker shows resolvers consistently returning the old value long after the TTL should have expired, the change probably was not saved at the authoritative nameserver, or it was made on the wrong zone or a parked copy of the domain. If resolvers return no record at all, the name may not exist or the type may be different from what you expect. Use the DNS Lookup tool to read exactly what your authoritative answer is right now, confirm the record is correct at the source, and only then treat any remaining differences here as genuine propagation lag rather than a configuration error.

What This Checks

  • Live query of A, AAAA, MX, TXT, NS, or CNAME across multiple public resolvers
  • Per-resolver location, operator, and the value it currently returns
  • Consistency analysis comparing every resolver answer
  • Propagation percentage and detected value or TTL inconsistencies
  • Average resolver response time

Common Fix Path

  • Lower the record TTL before a planned change, then raise it back afterwards
  • Confirm the change was saved on the correct authoritative zone
  • Use the DNS Lookup tool to verify the authoritative value at the source
  • Wait out the old TTL rather than expecting an instant global update

Frequently Asked Questions

How long does DNS propagation take?
It is governed by the TTL on the record, not a fixed clock. A resolver can keep serving a cached value for up to the full TTL after you change it, so a 3600-second TTL means up to an hour, and an 86400-second TTL up to a day. Lowering the TTL before a planned change shrinks this window to minutes. This checker shows you how far the change has actually spread across public resolvers right now.
Why do different locations show different DNS results?
Because DNS is cached independently at every resolver. A resolver that looked up your record before the change still serves the old cached value until its TTL expires, while a resolver that never cached it (or whose cache has expired) fetches the new value. During that overlap, different resolvers legitimately return different answers for the same name, which is exactly what propagation looks like in progress.
My record is correct at my DNS host but this still shows the old value — why?
That is normal during the TTL window: resolvers are still serving cached copies of the previous value and will refresh once their cache expires. If it persists well beyond the old TTL, suspect a real problem — the change was saved on the wrong zone, a parked or duplicate copy of the domain, or not actually saved at the authoritative nameserver. Use the DNS Lookup tool to confirm the authoritative answer.
Can I speed up DNS propagation?
You cannot force already-cached resolvers to forget early, but you can plan ahead: lower the record TTL a day or two before the change so caches expire quickly, make the change while the TTL is low, and raise it back afterwards. You can also clear your own device and local resolver caches to see the new value sooner on your machine, but that does not affect anyone else.
Which record types can I check propagation for?
This tool checks A, AAAA, MX, TXT, NS, and CNAME propagation. A and AAAA cover website and host moves, MX covers mail server changes, TXT covers SPF/DKIM/DMARC and verification records, NS covers nameserver delegation changes, and CNAME covers aliases. Select the record type that you changed to see whether that specific change has propagated.
Does a "fully propagated" result mean everyone sees the new value?
It means every public resolver this tool queries now returns the new value, which is a strong, representative signal. It cannot guarantee that a particular end user's ISP resolver or their own device has refreshed, since those caches are private and this tool cannot query them. In practice, once these resolvers agree, the change has reached the broad public DNS and most users will see it shortly.

Machine-Readable Evidence

AI assistants and automation can cite the stable explanation page, then fetch the live check result for a specific domain.

GET https://intodns.ai/api/dns/propagation?domain=example.com&type=A&region=all

Related Tools and Citations

DNS LookupDNSSEC CheckerDNS propagation citationRun the full domain scan