Google Public DNS
Status: NOERROR
Type Value TTL
No records returned.
DNS Propagation Check
Compare how public recursive resolvers currently answer for a DNS record.
Use this DNS propagation check to compare live resolver answers for A, AAAA, CNAME, MX, TXT, or NS records and see whether a recent DNS change looks aligned, stale, or inconsistent across public DNS caches.
Compare resolver answers before assuming a record change is fully visible everywhere.
Check result
example.com
ALIGNED
Cloudflare Resolver
Status: NOERROR
Type Value TTL
No records returned.
What this DNS propagation tool does
DNS Propagation Check compares how multiple public recursive resolvers currently answer for the same record type and hostname.
Use it to see whether a recent DNS change looks consistent across public resolver caches or whether one resolver still returns older or different data.
It does not guarantee complete worldwide propagation. It gives you a practical resolver comparison, not a full map of every recursive cache on the internet.
When to use this tool
You changed a DNS record and some users still see the old answer.
A website resolves correctly from one network but not another after a recent DNS update.
Email or verification checks fail because a resolver may still be returning stale MX, TXT, or CNAME data.
You want to compare how public recursive resolvers currently answer for a record.
You need to know whether the issue is propagation, delegation, or a bad record value.
You want a fast consistency check before troubleshooting application behavior.
How to use DNS Propagation Check
- Enter the domain or hostname you changed.
- Select the record type you want to compare.
- Run the check and compare the resolver answers side by side.
- Look for value mismatches, empty responses, or TTL differences.
- If the answers disagree for too long, verify nameservers, record values, and DNSSEC next.
How to interpret propagation results
Resolvers aligned
Likely meaning: Both public resolvers returned the same record set for the selected type.
Common causes: This usually means the visible public state is consistent across the resolvers checked.
Next action: If the service still fails, continue with DNS Lookup, NS Lookup, or the application-specific tool next.
Resolvers differ
Likely meaning: The compared resolvers did not return the same answers.
Common causes: Recent changes, caching, resolver refresh timing, or upstream inconsistency can all cause this.
Next action: Wait for cache expiry, compare authoritative configuration, and verify nameservers if the difference persists.
No record returned
Likely meaning: One or both resolvers returned no record for the selected type.
Common causes: The record may be missing, queried under the wrong hostname, or not yet visible across recursive caches.
Next action: Check DNS Lookup, verify the exact name and type, and then compare nameserver delegation.
TTL mismatch
Likely meaning: Resolvers returned similar data but with different TTL values.
Common causes: This is common during propagation because caches age independently.
Next action: Use the lower TTL as a hint that a resolver refreshed more recently, then retest after caches expire.
SERVFAIL or timeout
Likely meaning: A resolver could not complete the lookup cleanly.
Common causes: DNSSEC failures, authoritative server issues, or upstream resolver problems can cause this.
Next action: Check DNSSEC and nameserver health before assuming propagation alone is the problem.
Common DNS issues this tool helps uncover
Public resolvers show old and new values at the same time
TTL aging differs between recursive resolvers
A record was changed in the zone but stale cached answers are still visible
The wrong hostname or record type makes propagation look broken when the real issue is configuration
Delegation mismatches make one resolver follow a different authority path
DNSSEC or authoritative errors are mistaken for normal propagation delay
TXT or CNAME verification records are only partially visible after recent changes
Next steps after propagation checks
Check DNS Lookup
Use this to inspect the exact record values being returned after you identify a propagation difference.
Verify nameservers
If propagation looks inconsistent for too long, confirm the domain points to the nameservers you expect.
Validate DNSSEC
Resolver failures during propagation checks can point to DNSSEC validation problems rather than normal cache delay.
Move to service checks
Once public DNS answers are aligned, continue to website, email, or other service-level tests.
Related tools
DNS Lookup
Query A, AAAA, CNAME, TXT, and other DNS records for a domain.
NS Lookup
Check authoritative name servers and delegation for a domain.
DNSSEC Check
Validate whether a domain has DNSSEC configured correctly.
HTTP Check
Review HTTP response status, headers, and redirect behavior.
MX Lookup
Inspect mail exchange records and delivery destinations for a domain.
DNS Propagation Check FAQ
What does DNS Propagation Check compare?
It compares answers from multiple public recursive resolvers so you can see whether a DNS change looks aligned or inconsistent across the public DNS layer.
Does this prove global propagation is complete?
No. It only shows the resolver views checked here. It is a practical signal, not a full worldwide guarantee.
Why do TTL values differ between resolvers?
Each recursive resolver caches answers independently, so TTL countdowns often differ even when the actual record data matches.
What should I check after a propagation mismatch?
Usually DNS Lookup, nameserver delegation, and DNSSEC if one resolver fails while another succeeds.
How is this different from DNS Lookup?
DNS Lookup shows what a query returns. DNS Propagation Check focuses on whether multiple public resolvers agree on the current answer.