DNS Propagation Checker
Query four public DoH resolvers at once to confirm whether an A, AAAA, MX, TXT, CNAME, NS, SPF, or DMARC record has propagated consistently, or is still spreading after a change.
Workflow
Run check
Inspect a live record
Results are generated on demand so you can verify the current public configuration.
What is DNS propagation?
When you change a DNS record, the new value has to spread to resolvers around the world.
Each resolver caches the previous answer until its TTL expires, so a change is not visible
everywhere at the same moment.
Why query multiple resolvers?
Checking several independent public resolvers at once shows whether they agree. If every
reachable resolver returns the same answer, the record has propagated. If they differ, the
change is still rolling out.
How long does DNS propagation take? +
Propagation is bounded by the TTL of the record you changed plus caching at each resolver. It usually completes within minutes to a few hours, but can take up to 24-48 hours for records with long TTLs.
Why do resolvers show different answers? +
Different public resolvers cache records independently. Right after a change, some may still serve the old value while others have picked up the new one. An inconsistent verdict means propagation is still in progress.
Which resolvers are queried? +
Google (8.8.8.8), Cloudflare (1.1.1.1), Quad9 (9.9.9.9), and OpenDNS (208.67.222.222) over their public DNS-over-HTTPS endpoints. If one resolver is unreachable it is marked unavailable and the others still return.