Use this DNS exit check to observe the public exit used by recursive DNS requests reaching a controlled authoritative DNS server. Compare DNS and site exits separately for IPv4 and IPv6; a difference is not automatically a DNS leak or configuration error.
Checks public recursive DNS exits and compares each address family with the matching site exit.
This starts one random DNS and browser connection request. Records are used only for this check and expire automatically.
A DNS exit check observes the public source used when a recursive DNS request reaches a controlled authoritative DNS server. It compares that path with the site's IPv4 and IPv6 exits separately; it is not a physical-location test or an automatic DNS-leak verdict.
Compare IPv4 DNS only with the site's IPv4 exit, and IPv6 DNS only with its IPv6 exit. When a matching family is unavailable, the result remains inconclusive instead of treating cross-family addresses as a conflict.
Proxy rules, accelerators, secure DNS, dual-stack routing, and ISP resolvers can send DNS and HTTP through different networks. A difference describes this check's path relationship; review AI routing and WebRTC exits for more context.
The check begins only after you choose to start it and uses a random subdomain to reduce cache interference. Records needed for this result are retained only briefly and are not used to track a public IP over time.
Not necessarily. A public IP comes from this site's HTTP request, while a DNS exit comes from a recursive DNS request reaching the controlled authoritative DNS server. Network policies can make the paths differ.
An AI routing exit observes HTTP/HTTPS traffic to a specific AI service. A DNS exit observes recursive DNS traffic while resolving a domain. They complement each other but are not interchangeable.
It can be. A dual-stack network can use different DNS, proxy, or routing policies for IPv4 and IPv6. This check displays them separately and compares each only with the matching site exit.
No. It only shows a difference in this check's paths. Review secure DNS, proxy coverage, dual-stack rules, and the actual network setup before drawing a configuration conclusion.
