DNS Propagation Checker - Verify DNS Changes Across Resolvers

What is DNS propagation?

When you change a DNS record, the change does not appear everywhere instantly. DNS records are cached by resolvers around the world for a period defined by the record's TTL (Time to Live). Until those caches expire, different DNS servers may return the old value or the new value depending on when they last checked. This transition period is called DNS propagation.

For email records specifically, propagation matters because:

• A new SPF record will not protect against spoofing until all checking mail servers see it.
• An updated DMARC policy change (e.g., from p=none to p=reject) is not enforced until fully propagated.
• A new MX record means some senders may still route email to the old mail server during propagation.

How long does DNS propagation take?

Record type	Typical propagation
A, AAAA	A few minutes to a few hours (depends on TTL)
TXT (SPF, DMARC)	A few minutes to a few hours
MX	A few minutes to a few hours
NS (nameserver changes)	1 to 24 hours
Negative cache (NXDOMAIN)	Can persist for hours depending on negative TTL

Propagation is faster when the record's TTL is low. Before making a time-sensitive change, lower the TTL to 300 seconds a day in advance. After the change is confirmed, raise it back to 3600 or higher.

How this tool checks propagation

This tool queries two major public DNS resolvers directly using their DNS over HTTPS (DoH) APIs:

• Google Public DNS (8.8.8.8) - one of the most widely used public resolvers globally
• Cloudflare DNS (1.1.1.1) - another widely used resolver with fast global coverage

If both resolvers return the same result, your change has likely propagated. If they differ, propagation is still in progress. For complete global propagation testing, tools that query 20+ resolvers worldwide give a more thorough view.

FAQ

My record looks correct in my DNS panel but this tool shows the old value - why?

The DNS change was published at your DNS provider, but public resolvers have cached the old value until the TTL expires. Wait for the TTL to count down (check what TTL was set on the record before you changed it), then run the check again.

How can I speed up DNS propagation?

Before making a change, lower the TTL of the record to 300 seconds and wait for that TTL to pass so caches expire. Then make the change. The new value will propagate within 5 minutes from that point. This requires planning ahead - you cannot speed up propagation retroactively.

Should Google and Cloudflare always agree?

Once propagation is complete, yes - both should return the same current records. If they disagree, either propagation is still in progress, or there is an inconsistency at the authoritative DNS server (e.g., different values at different nameservers). Check your DNS provider to confirm the record is set correctly.