DNS Propagation
Enter a domain and record type and I query several public resolvers (Cloudflare and Google) over DNS-over-HTTPS, comparing answers to tell whether the change has propagated or still differs.
I query the same name and type on Cloudflare (1.1.1.1) and Google (8.8.8.8) over DNS-over-HTTPS; the requests go encrypted to those resolvers and do not pass through any redzilla server.
| Resolver | Status | TTL | Answer |
|---|
Queries over DNS-over-HTTPS (Cloudflare · Google) · the rest of the site runs locally.
How it works
The tool queries the same name and record type (A, AAAA, CNAME, MX, TXT or NS) on two public resolvers at once: Cloudflare (1.1.1.1) and Google (8.8.8.8), both over DNS-over-HTTPS (RFC 8484). It shows the status, TTL and answers from each resolver side by side.
For the verdict it normalizes each answer set (lowercase, no trailing FQDN dot, TXT without quotes) and compares the sets regardless of order: if every resolver returns exactly the same data, the change has propagated; if they differ, the record is still propagating, usually because some resolver keeps serving the old answer from its cache until the TTL expires.
Example: verifying an IP change for a website
- You pointed the A record of
www.example.comto a new server. Enter the domain, pick type A and compare. - If Cloudflare answers the new IP while Google still returns the old one, the status is propagating: the Google cache has not expired yet.
- The TTL in the table tells you at most how many seconds until that resolver refreshes; once both return the new IP, the verdict switches to propagated.