DNS Leak Test
The DNS leak test checks whether DNS queries follow your proxy or VPN route instead of going to a local ISP resolver. Privacy teams, automation operators, and remote workers use it to confirm that their browsing domains are not exposed outside the intended tunnel before running sensitive sessions.
Run a DNS leak test right after setting up a proxy or VPN, before logging into accounts or collecting data. The visible IP can look correct while DNS requests still reveal the original provider or an unexpected location. If the result shows resolvers outside the country you expected, fix the browser, operating system, or proxy client settings before trusting the session.
Run the result against the exact browser, device, proxy protocol, and target country you plan to use in production. A clean result here is not a ranking promise, but it catches the configuration mistakes that usually create blocked sessions, wrong geo signals, DNS leaks, or inconsistent fingerprints.
For repeat workflows, record the visible IP, ASN, DNS route, latency, and warning state before and after each proxy change. That gives QA, scraping, SEO, ads, and account teams a comparable baseline instead of relying on a single one-off check.
When troubleshooting a blocked session or unexpected platform response, work through the stack in order: confirm the port is reachable, verify the exit IP and ASN, check DNS resolver, inspect request headers, and then compare browser fingerprint and timezone. Skipping layers leads to misdiagnosis — a timeout at the port level looks similar to a cookie checkpoint at the application layer but the fix is completely different.
Mobile proxy workflows behave differently from datacenter ones because CGNAT means multiple physical users share the same outbound IP range. Platforms treat these IPs with higher inherent trust, but that trust can erode if the same session triggers unusual behavior like very high request rates, mismatched timezones, or browser fingerprints that do not match a real mobile device. Use these diagnostic tools to verify the whole configuration, not just the IP.
Advanced DNS leak detection — check if your DNS requests are properly secured.
Analyzing DNS Security...
Checking your DNS routing and leak status
What is a DNS Leak?
A DNS leak occurs when your DNS requests handle your VPN or proxy and go directly to your ISP. This exposes your browsing activity even when you think you're protected.
Why DNS Leaks Matter
Your ISP can see many websites you visit. Third parties can track your browsing. It defeats the purpose of using a VPN or proxy, and can reveal your actual location.
How to Fix DNS Leaks
Use a VPN or proxy with built-in DNS protection. Configure custom DNS servers (1.1.1.1, 8.8.8.8). Proxy Poland mobile proxies route all DNS through the proxy connection.
Understanding Results
If you're not using a VPN/proxy, seeing your ISP's DNS is normal. If you ARE using privacy tools and still see your ISP's DNS — you have a DNS leak.
Frequently asked questions
How DNS leaks happen, what the test detects, and how mobile proxies prevent them.
What is a DNS leak?+
When your traffic supposedly goes through a proxy or VPN but DNS lookups still go to your ISP's resolver, your real location and ISP are exposed even though your data traffic looks anonymous. The DNS leak test detects which resolver actually answered your queries.
How does the DNS leak test work?+
Your browser performs lookups for unique randomized hostnames against our server. We see which DNS resolver IPs reached us. If the resolver IP matches your ISP and not your proxy/VPN's resolver, you have a leak.
Why are leaked DNS requests bad?+
DNS reveals every domain you visit. Even if your HTTPS data traffic is hidden, the resolver answering for `your-bank.example` knows you visited that bank. For multi-account, scraping, or privacy work, that's a hard fingerprint.
Can a mobile proxy leak DNS?+
Only if your client app is misconfigured. Proxy Poland mobile proxies forward DNS through the carrier's resolver by default — same resolver every other phone on that operator uses. Misconfiguration usually = your OS still uses local DNS while your HTTP traffic goes through the proxy.
How do I fix a DNS leak when using a proxy?+
If you connect via SOCKS5, set the client to send DNS over the proxy (`proxy-dns yes` in cURL, `--proxy-dns` in some browsers, or use SOCKS5h instead of SOCKS5 in libraries). For browsers, use SOCKS5h or set `network.proxy.socks_remote_dns=true` in Firefox.
What's the difference between DNS leak and IPv6 leak?+
Both expose your real identity. DNS leak = lookups go around the proxy. IPv6 leak = your real IPv6 address goes around the proxy because the proxy is IPv4-only and your OS prefers IPv6. Disable IPv6 on your client when using IPv4-only proxies.
What is WebRTC leak and is it tested here?+
WebRTC is a browser API that can reveal your local LAN IP and sometimes your real public IP via STUN/TURN servers, even with a proxy. Some DNS leak testers also flag WebRTC leak; ours focuses on resolver leaks specifically. Disable WebRTC in your browser if it's not needed.
Can browser extensions cause DNS leak?+
Yes. Some extensions (especially privacy/ad-blocker extensions that proxy DNS through their own services) override your proxy DNS. If you see an unexpected resolver in the test, disable extensions and retest.
Are DoH (DNS-over-HTTPS) and DoT safer?+
Yes, but they don't fix proxy leaks. DoH/DoT encrypts DNS in transit so your ISP can't see queries — but if your client uses your default DoH (e.g. Cloudflare, Google) instead of routing DNS through the proxy, that resolver still sees your queries.
Why does my real IP show in the DNS test even with proxy?+
Two reasons: (a) DNS goes around the proxy entirely (DNS leak — see fix above), or (b) the test page made a non-DNS connection (image, ping, fetch) that skipped your proxy. The second is a client config issue — make sure all traffic from the test page goes through your proxy.
Does using a custom DNS server (1.1.1.1, 8.8.8.8) protect me?+
Partially. Custom DNS keeps queries away from your ISP, but Cloudflare or Google then see your queries instead. If your goal is hiding queries from anyone, route DNS through the proxy itself, not a third-party public resolver.
How often should I run a DNS leak test?+
Every time you change your proxy/VPN setup, browser, OS network settings, or extensions. A test from one moment doesn't guarantee no leak after a config change. For production scraping/multi-accounting, automate a leak check before each long session.