Consistent
Resolvers agree on the returned value. This does not guarantee every ISP resolver has expired its cache.
DNS diagnostics
DNS Propagation Checker
Compare a DNS record across multiple public resolver networks. This helps you identify differing cached answers, missing records, and resolver timeouts after a DNS change.
Multiple networksCompare independent public DNS resolver services.
Answer comparisonSee which resolvers return the same value.
TTL and latencyInspect cache timing and request response time.
Check DNS propagation
Choose a record type and compare the current answers.
Enter a domain to begin.
Resolver results will appear here
Every card represents a separate public resolver network queried by the Netest server.
How to interpret the results
Different
At least one resolver returns a different value. Check TTL, authoritative nameservers, and recent DNS changes.
Not found
The resolver completed the query but returned no answer for the selected record type.
Measurement scope
These are public anycast resolver observations. Exact city-level testing requires dedicated probes in those regions.
DNS propagation explained
When you change an A, AAAA, CNAME, MX, TXT, or other DNS record, recursive resolvers may continue serving the previous answer until its time to live expires. This is why a website or mail service can appear updated from one network while another network still sees the older value.
This checker sends the same record query to several independent public resolver networks and places their answers side by side. A consistent result means the tested resolvers currently agree. A different result is a useful signal to inspect the authoritative nameservers, the record TTL, delegation, and the exact time of the change.
Recommended troubleshooting workflow
- Confirm that the record was edited at the authoritative DNS provider.
- Check the NS records to verify which nameservers are authoritative.
- Run this comparison for the exact hostname, not only the parent domain.
- Compare the returned values and TTLs with an authoritative lookup.
- Allow the previous TTL window to pass before treating a temporary difference as a failure.
Frequently asked questions
Does DNS propagation happen from one central server?
No. DNS answers are cached independently by recursive resolvers, ISP networks, operating systems, browsers, and local devices. The visible result depends on which resolver a client uses.
Why can two locations show different DNS answers?
They may be using different recursive resolvers, or one resolver may still have a cached answer. Delegation problems, split-horizon DNS, DNSSEC errors, and provider-specific routing can also create differences.
Does a green result guarantee that my website works?
No. This tool checks DNS answers only. Use the SSL Checker, HTTP Header Checker, ping, or port tools separately to investigate certificate, web-server, reachability, and service problems.
Are the resolver locations exact cities?
The first version compares public anycast resolver networks. Anycast traffic can be handled by different facilities, so the network label should not be interpreted as an exact physical probe location.
Choose the right DNS record
The record type determines what kind of change you are checking. Select the record that matches the service symptom instead of relying only on an A-record test.
Reading the status markers
A resolved result means the selected record was returned. A different answer means the value does not match the majority observed by this check. A not-found result is a completed DNS response with no answer for that type. A timeout or error means the resolver could not be measured in this run.