Lookup setup
Check a DNS record
Querying public resolvers…Google, Cloudflare, AdGuard and DNS.SB are checked in parallel.
Resolver report
Live DNS answers
Resolver agreement is useful evidence, not an absolute geographic guarantee. Public anycast resolvers may answer from different network locations, and CDNs can intentionally return different records.
This browser
Recent lookups
Make sense of the result
DNS propagation is really cache expiration
DNS records are cached for their TTL (time to live). After a record changes, some recursive resolvers may still serve the previous cached value until that TTL expires. This checker compares several large public resolver networks at the same moment.
Website addresses
A maps a hostname to IPv4; AAAA maps it to IPv6. Multiple answers can be normal behind CDNs or load balancers.
Aliases and delegation
CNAME points one hostname at another. NS identifies the authoritative nameservers responsible for a DNS zone.
Email and verification
MX selects receiving mail servers. TXT commonly carries SPF, DKIM, DMARC, ownership, and service verification data.
Zone authority
SOA describes the zone’s primary authority and timing values. Its serial helps indicate whether authoritative copies agree.
How to check a DNS change correctly
- Enter only the hostname you changed.For example, check
www.example.comseparately fromexample.com. - Select the exact record type.An A lookup cannot confirm an MX or TXT change.
- Add the expected value.This distinguishes propagation from legitimate CDN or multi-record variation.
- Compare after the old TTL.If a resolver still shows the previous answer, wait until its cached response can expire.
Frequently asked questions
What does “fully propagated” mean here?
Every responding resolver returned the expected value. A resolver that failed to respond is shown separately and is not silently treated as a match.
Why do different resolvers return different IPs?
This may indicate cached old data, but CDNs and geo-aware DNS can deliberately return different IPs. Enter the value you expect for a more useful verdict.
How long should I wait after changing DNS?
Use the TTL that existed before the change as your best guide. Changes often become visible within minutes or hours, but caches and delegation changes may take longer.
Can this checker modify or flush DNS?
No. It performs read-only public lookups. Only your DNS provider can change records, and third-party resolver caches cannot normally be manually flushed by this page.
Why is an expected MX or TXT value not matching?
Use the complete value shown by the resolver, including an MX priority or TXT quoting where applicable. You can first run without an expected value and copy the displayed format.