Check whether DNS changes are visible across multiple major public resolvers. This is useful after updating A, AAAA, CNAME, MX, TXT, NS, or SOA records and wanting to know whether the new value is showing up in the real world yet.
A propagation checker is different from a simple DNS lookup. Instead of asking just one resolver for one answer, it compares multiple public resolver paths to help you see whether a new record value is appearing consistently or whether different caches are still returning older results.
Weighted score
—
Primary public resolvers count more than filtered variants.
Propagation %
—
Weighted real-world propagation signal.
Consensus Value
—
Most common answer from primary resolvers first.
Query
—
Current domain + record type checked.
Best for
DNS changes and migrations
Common checks
Website, mail, TXT verification
Runs from
Browser + public resolvers
Useful after
Record edits and nameserver changes
Resolver Results
Results appear as each resolver finishes. DNS64 was removed from live checks to avoid slow or misleading browser behavior in normal public-web checks.
Ready
Checking major public resolvers
Resolver
Result
Weight
TTL
Latency
Ready
Enter a domain, choose a record type, and run the check.
—
—
—
How scoring works
Standard public resolvers are weighted highest because they better reflect common public DNS resolution paths. Security and Family resolvers still count, but they count less because they may intentionally filter or alter some domains.
Why DNS64 was removed
DNS64 is intended for IPv6-only and NAT64 scenarios, not as a normal public browser check path. Removing it avoids pointless timeouts and makes the tool feel faster and more representative for everyday DNS troubleshooting.
What DNS propagation means in practice
DNS propagation is the period during which different resolvers stop serving old cached values and begin returning your updated DNS records. In plain terms, one resolver might already show the new A record while another still returns the old address. That is why a site can look correct for one user but still appear broken for another user somewhere else.
This checker helps by comparing multiple resolvers at once instead of forcing you to check each one manually. That is especially helpful after changing hosting providers, mail configuration, CDN targets, verification TXT records, or nameservers.
Common use cases
Confirming website IP changes after moving to a new server
Checking MX records after switching email providers
Verifying TXT records for Google, Microsoft, or other services
Comparing results after updating nameservers
Checking whether a CNAME target is visible globally
What can delay propagation?
Resolver cache still holding older records
Higher TTL values slowing refresh timing
Recent DNS provider or nameserver changes
Registrar updates not fully reflected yet
Resolver-specific filtering or regional behavior
Why some resolvers return different answers
Different resolvers can legitimately show different answers during propagation. Public DNS systems do not refresh at exactly the same moment. One resolver may have already expired the old cache while another still serves it. Some resolvers may also apply their own policies, filtering, or security adjustments, especially family-safe or security-focused variants.
That is why weighted propagation is useful. It avoids letting less representative resolver variants dominate the score while still giving you secondary signals that can be useful in edge cases.
How to interpret the results
A high weighted percentage usually means your DNS change is visible across most common public resolver paths. A lower percentage often means the update is still propagating, one or more resolvers are serving cached data, or the expected value does not match the actual live result yet.
The consensus value is especially helpful when you want a quick answer to the question, “What are most resolvers seeing right now?” If your expected value matches the consensus and the weighted percentage is high, that is usually a strong sign that the change is taking hold.
Best practices after DNS changes
Lower TTL before a planned migration when possible.
Update records carefully and verify syntax.
Check both direct lookup and propagation views.
Wait and retest if only some resolvers show the new value.
Document the old and new values for comparison.
Why this page is useful
A thin propagation checker only spits out resolver answers. A stronger page explains what those differences mean, why weights matter, and how to use the data in a real troubleshooting workflow. That added context makes the tool more helpful to both technical and non-technical users.
Why trust InstantQR tools?
InstantQR tools are designed to be fast, practical, and privacy-conscious. This propagation checker runs from the browser using public DNS-over-HTTPS endpoints and presents results in a cleaner format that is easier to interpret than raw resolver responses alone.
That makes it useful for quick checks, migration validation, support tickets, and verification workflows without requiring an account or unnecessary friction.
Related Network Tools
Use these alongside propagation checks when you want a fuller picture of DNS state, ownership, routing, or HTTP behavior.
DNS propagation is the time it takes for updated DNS records to become visible across different DNS resolvers around the internet.
What record types can I check here?
You can check A, AAAA, CNAME, MX, TXT, NS, and SOA records with this DNS propagation checker.
Why do some resolvers show different results?
Resolvers may return different answers because cached DNS records expire at different times, propagation is still in progress, or your DNS update has not reached every resolver yet.
Why are some resolvers weighted differently?
Standard public resolvers better represent common DNS resolution paths. Security and family-safe resolvers can apply additional filtering, so they are useful secondary signals but should not dominate the score.
How do I know if my DNS change has propagated?
If several resolvers match your expected value and the weighted propagation percentage is high, your update is likely visible across most real-world public DNS paths.
