Same DNS question
The domain and selected record type are encoded as a standard DNS-over-HTTPS request and sent to each named resolver.
Selected public resolvers · TTL evidence
See which DNS answer each resolver has now.
Compare one record across Cloudflare, Google Public DNS and AdGuard's non-filtering resolver. See the returned values, remaining TTL and response time side by side.
Compare DNS answersOne question, three resolvers
Choose a hostname and record type.
Use the exact name you changed. For example, check www.example.co.uk for a website record or example.co.uk for MX.
A focused comparison. These are three named public recursive resolvers, not measurement points in every country or network.
Why answers change at different times
TTL is a cache countdown, not a delivery timer.
A resolver may keep an earlier answer until its cached lifetime ends. Another resolver that looked up the name later can have a different countdown—or already hold the new record.
Read the DNS-over-HTTPS caching standardResolver Aolder answer
Resolver Bolder answer
Resolver Crefresh soon
Each cache refreshes on its own schedule.
A transparent boundary
What this comparison does—and what it cannot claim.
Bounded evidence
Responses have short timeouts and size limits. Up to 12 values are displayed for each resolver.
Remaining TTL
The smallest relevant TTL is shown after accounting for an HTTP cache age when one is reported.
Not the whole world
Three public resolver answers cannot represent every country, ISP, company network, browser or device cache.
DNS propagation questions
Read the evidence without over-reading it.
Is this a worldwide DNS propagation test?
No. It compares the answers returned by the three named public resolvers shown here. It cannot represent every resolver, network, device or location.
Why can public resolvers show different answers?
Recursive resolvers cache DNS data independently. Recent record changes, TTL expiry, negative caching and temporary lookup failures can make their answers differ for a while.
What does the TTL shown here mean?
It is the remaining cache lifetime in that resolver's response, adjusted for an HTTP Age header when present. It may be lower than the original TTL configured at the authoritative DNS service.
Does agreement prove everyone sees the same record?
No. Agreement is useful evidence from these selected resolvers at one moment. Local, ISP, enterprise and other public caches may still hold a different answer.