DNS leak test for proxy & VPN sessions
Domain lookups may bypass your proxy tunnel and hit ISP resolvers. This test records which DNS servers actually resolve probe hostnames and compares their geography to your exit IP.
Designed for MMO, scraping, and antidetect workflows on CheckProxy.org. Resolver list is heuristic (public DoH resolvers may be hidden).
Current connection
IP
—
Detected DNS servers
| DNS server IP | Country — ISP |
|---|---|
| Testing… | |
FAQ — DNS leak test
Common questions about DNS leaks and how DNS resolvers are detected.
A DNS leak occurs when a device sends domain resolution requests through an ISP resolver instead of through the VPN or proxy path configured on the connection.
A DNS leak test shows which DNS servers resolve test domain queries and whether resolver location matches the expected connection path.
The test helps compare which DNS resolvers are active during a VPN or proxy session versus a direct connection.
We generate unique test hostnames; your browser must resolve them through your DNS resolver. Our test server logs the resolver IP and looks up its location and ISP.
The active resolver depends on OS settings, browser Secure DNS (DoH/DoT), VPN client configuration, and local network DHCP. Different resolvers may appear when DNS is not routed through the same path as web traffic.
A DNS leak does not always expose your public IP, but it can reveal which DNS provider handled the query and its approximate geographic region.
Many networks use multiple resolvers for redundancy. Browsers with Secure DNS (DoH) may also query Cloudflare or Google — we hide those public resolvers and prioritize ISP/VPN resolvers like common leak check tools.
Yes. If the VPN client or system routes DNS outside the tunnel, queries may still reach ISP resolvers even while other traffic uses the VPN.