Cloudflare DNS
Queries Cloudflare's public DNS-over-HTTPS service and shows the answers returned for the selected record type.
DNS Propagation Checker
Compare DNS answers from multiple independent resolvers to spot propagation differences.
Result
Compare DNS answers across independent resolvers
The DNS Propagation Checker queries Cloudflare DNS, Google Public DNS and the resolver available to the Smart Web Utility server. Comparing those answers helps reveal when recursive resolvers are still caching different values after a DNS change.
Google Public DNS
Queries Google's public DNS resolver independently so you can compare its current answer with Cloudflare and the server resolver.
Server resolver
Runs a lookup from the hosting environment as a third comparison point. This is useful for spotting disagreement between public recursive paths.
Common record types
Compare A, AAAA, MX, TXT, CNAME, NS and CAA answers depending on the DNS change you are troubleshooting.
What “DNS propagation” actually means
DNS does not update through a single worldwide push. Recursive resolvers cache answers for a period defined by TTL values. After an authoritative DNS change, one resolver may refresh quickly while another continues serving an older cached record until its cache expires. That temporary disagreement is commonly described as DNS propagation.
How to interpret the comparison
If all resolvers return the same expected answer, the change is likely visible through those recursive paths. If one resolver still returns the previous value, it may still have a cached answer. If every resolver returns an unexpected value, check the authoritative DNS configuration rather than assuming the issue is only cache delay.
A resolver returning no answer can also be valid for a record type that does not exist. Compare the selected record type with the records you actually intended to publish.
Useful propagation checks after common changes
Website migration
Compare A and AAAA records after changing hosting, CDN or origin addresses. Make sure the expected new endpoint is appearing consistently.
Email provider change
Compare MX and TXT records after changing mail routing, SPF or provider verification records.
Nameserver change
Compare NS records, then confirm the registrar is delegating to the intended authoritative nameservers.
Certificate issuance
CAA or validation-related DNS changes can affect certificate issuance. Compare the published record before retrying the certificate workflow.
Important limitation: this is not a worldwide node map
This checker intentionally compares three resolver paths rather than pretending to represent every country or ISP. Matching results here do not prove that every recursive resolver worldwide has refreshed. For a direct record lookup from one resolver, use the DNS Checker.
DNS troubleshooting guide
Related website tools
Frequently asked DNS propagation questions
How long does DNS propagation take?
There is no single fixed duration. Resolver cache state and the previous TTL are major factors. Some resolvers may refresh quickly while others continue serving an older cached value until that cache expires.
Why do Cloudflare and Google show different answers?
They are independent recursive resolvers with separate caches. One may have refreshed the record after your change while the other is still serving a cached answer.
Does clearing my browser cache fix DNS propagation?
Not necessarily. DNS can be cached by the operating system, local resolver, ISP or public recursive service. Browser cache is only one possible layer.
Should I keep changing the DNS record while waiting?
Repeated changes can make troubleshooting harder. First verify the authoritative configuration is correct, then allow existing caches to expire unless there is a genuine configuration mistake to fix.