DNS propagation
DNS propagation checker
Compare live answers from nine public DNS resolvers to see whether a record change has converged and where stale or missing responses remain.
Live comparison
Propagation results for A
Responses are collected concurrently and may take a few seconds.
The DNS propagation check failed. Please try again later.
| Resolver | Status | DNS answer | TTL | Response time |
|---|
How to read the check
What DNS propagation means
Recursive DNS resolvers cache answers for the record's TTL. After a change, some providers can continue returning an older answer until their cached copy expires.
This comparison checks independent public resolver networks. Matching answers are a strong convergence signal, but they do not represent every geographic ISP or private network.
Inspect one resolver in the DNS lookup toolpublic resolver networks
supported record types
uncached check request
DNS propagation FAQ
Why do resolvers return different answers?
Resolver caches expire independently. During a DNS change, a resolver whose cached TTL has not expired may still return the previous record.
When is a DNS change fully propagated?
Propagation is usually considered stable when major public resolvers return the intended answer and old TTL windows have elapsed. Local ISP and enterprise caches can still differ temporarily.
Which DNS records can I check?
The checker supports A, AAAA, CNAME, MX, TXT, and NS records. Use the standard DNS lookup tool for detailed SOA and CAA inspection.
Does a failed resolver mean the domain is down?
No. One provider can time out or reject a request while other resolvers work normally. Compare the complete result set and retry before diagnosing an outage.