Enter a domain and a record type to query Cloudflare and Google public DNS side by side and compare the answers each resolver returns.
The checker sends the same query to two major public resolvers — Cloudflare DNS-over-HTTPS and Google Public DNS — and lists each resolver's answers with their TTLs. Resolvers cache answers for the length of each record's TTL, so during propagation the two can legitimately return different results until the old cached answers expire. The comparison shows what these two resolvers currently return; it is not a survey of every resolver worldwide, and a match here does not guarantee every local resolver has caught up yet.
Why do the two resolvers show different answers? Each resolver caches answers independently for the record's TTL. After a change, one resolver may have refreshed while the other still serves the cached old answer. The difference clears on its own as caches expire.
Does a match here mean propagation is finished everywhere? No. This page shows what two major public resolvers currently return, not every resolver worldwide. Local and ISP resolvers run their own caches and can lag behind.
What does the TTL column mean? TTL is the number of seconds a resolver may cache that answer. A high TTL means slower propagation of changes but fewer lookups; a low TTL means changes spread faster.