DNS Propagation Checker
Compare DNS answers and TTLs from Google and Cloudflare public resolver APIs.
Plain hostnames, underscored DNS labels, Unicode domains, and pasted http/https URLs are normalized before lookup.
Resolver comparison
DNS answers from the selected public resolvers will appear here.
Two resolvers are a comparison, not a world map
Different answers can reflect cache age, geo-aware DNS, load balancing, resolver policy, or an active change. Matching answers from Google and Cloudflare do not prove that every ISP cache has the same value.
Where the query goes
The DNS name is sent directly from your browser to Google Public DNS and Cloudflare's resolver endpoints. Yoryantra does not proxy the lookup, but those third-party resolver providers receive the request and apply their own logging and privacy policies.
DNS "propagation" is usually several caches aging at different times
After an A, AAAA, MX, TXT, CNAME, NS, SOA, or CAA change, recursive resolvers may continue serving cached data until that cache entry is refreshed. There is no single global propagation clock and no single resolver that can certify what every network sees.
A returned TTL is the TTL visible in that resolver response at query time. It is useful evidence, but it is not a countdown for every cache on the Internet and it does not reveal caches that were populated at different moments.
"No answer" and NXDOMAIN are different failures to diagnose
Found
The resolver returned at least one record of the requested type. CNAMEs or other answer records are shown separately when present.
NOERROR with no matching type
The name can exist while the requested record type is absent. That is different from saying the DNS name itself does not exist.
NXDOMAIN
DNS response code 3 means the queried name does not exist according to that resolver's current resolution result.
The browser-friendly JSON APIs are not the RFC 8484 wire format
RFC 8484 standardizes DNS-over-HTTPS using DNS messages over HTTPS. Google also exposes a web-friendly JSON endpoint at dns.google/resolve, and Cloudflare documents a compatible JSON representation for its endpoint. Cloudflare explicitly notes that the JSON format itself has no formal RFC.
These lookups use those JSON APIs because browsers can query and display record data without building binary DNS packets. For a protocol implementation or a critical interoperability path, use the RFC 8484 wire format rather than assuming every JSON provider behaves identically. RFC 8484 · Google JSON API · Cloudflare JSON API
Record values mean different things depending on the RR type
A IPv4 address AAAA IPv6 address CNAME Alias target MX Preference and mail exchanger TXT One or more DNS character strings NS Authoritative nameserver SOA Zone authority and timing fields CAA Certificate-authority authorization policy
Provider JSON formatting is kept visible rather than aggressively rewritten, especially for TXT, MX, SOA, and CAA values where spacing and quoting can carry presentation meaning.