Free network diagnostics
See whether your DNS resolver context looks consistent. The page makes five independent network probes — two HTTP IP lookups, one Cloudflare edge query, and three public DoH reachability checks — and tells you whether they all agree on your apparent network identity. Useful, but not the only DNS test you might want.
Result
Checking your DNS context…
Running five parallel network probes — two IP lookups and three public DoH reachability checks.
Two independent providers, asked the same question. They should agree.
Metadata Cloudflare's network reports for your connection.
Whether the three best-known public DNS-over-HTTPS resolvers are reachable from your browser, and how fast they responded.
| Provider | Reachable | RTT | Notes |
|---|---|---|---|
| Cloudflare | — | — | — |
| — | — | — | |
| Quad9 | — | — | — |
What this checks (and doesn't)
This page checks (1) whether two independent IP-lookup paths agree on your apparent public IP and country, (2) whether Cloudflare's edge sees you using their WARP DNS proxy, and (3) whether three major public DNS-over-HTTPS resolvers are reachable from your browser.
This page does not detect which DNS resolver your operating system uses by default — that requires a server controlling its own authoritative DNS infrastructure, which a static page like this one cannot do. For a comprehensive system-resolver leak test, see dnscheck.tools ↗ — they run the DNS-server-side infrastructure required for that check.
How this page works
This page makes five HTTPS requests on load: one to ipapi.co (with ipify.org as a fallback) for the public-IP lookup, one to 1.1.1.1 for the Cloudflare edge metadata, and one each to cloudflare-dns.com, dns.google, and dns.quad9.net for the DoH reachability checks. Each of those services sees your IP for the duration of its request.
Everyday Tools Hub does not log, store, or transmit any of the information shown on this page. Each DoH probe is a single DNS query for a known well-published hostname — no user data is sent to any resolver.
Check whether your DNS resolver context looks consistent — public IP, country, and DoH reachability across multiple providers.
These cover the most common questions about DNS context, what this page actually checks, and why a comprehensive system-resolver test needs different infrastructure.
FAQ
Five things in parallel: (1) your public IP via ipapi.co, (2) your public IP and Cloudflare datacenter via Cloudflare's edge trace endpoint, (3) reachability of Cloudflare's public DoH resolver, (4) reachability of Google's public DoH resolver, (5) reachability of Quad9's public DoH resolver. It then cross-references the two IP views, the two country views, and the three DoH probes to give you a single plain-English verdict.
FAQ
No — and we want to be honest about that. A comprehensive DNS leak test needs to know which DNS resolver your operating system uses by default, which requires a server controlling its own authoritative DNS infrastructure. Static pages like this one cannot do that. What this page CAN do is verify that your network identity is consistent across multiple independent observation paths and that public DoH endpoints are reachable from your browser. For a full system-resolver test, see dnscheck.tools — they run the DNS-server-side infrastructure required for the comprehensive check.
FAQ
Cloudflare WARP is Cloudflare's free consumer DNS-over-HTTPS proxy. If Cloudflare's edge trace endpoint reports your traffic as coming through WARP, it means you're already routing your DNS queries through an encrypted channel to Cloudflare's resolver. That's a privacy-positive setting — the page surfaces it as informational, not a warning.
FAQ
It means ipapi.co and Cloudflare's edge see different IP addresses for you. The most common reasons are dual-stack networks (the two providers happened to pick different IPv4/IPv6 families), staleness in their geo-IP databases, and CDN-level proxying. A mismatch is a signal worth checking, but it's almost never an actual DNS leak on its own — the WebRTC leak test is a better place to investigate VPN bypasses.
FAQ
Probably not. Many corporate networks, captive portals, and aggressive content blockers (like uBlock Origin's privacy-focused lists) intentionally block public DNS-over-HTTPS endpoints. If only one or two of the three providers are unreachable, that's almost always one of those reasons. If all three are unreachable, your network is restricting public DoH globally, which is a network policy decision rather than a leak.
FAQ
No. The page makes five HTTPS requests on load — to ipapi.co (with ipify.org as a fallback), Cloudflare's 1.1.1.1, cloudflare-dns.com, dns.google, and dns.quad9.net. Each of those services sees your IP for the duration of its request. Everyday Tools Hub does not log, store, or transmit anything about your visit beyond what your CDN already sees as part of any web request.
Explore other utilities in the Everyday Tools Hub library.