DNS Leak Test
Check if your proxy or VPN is leaking your real IP via DNS queries or WebRTC. Compares your HTTP visible IP against WebRTC-discovered IPs.
Checking…
Running DNS and WebRTC checks…
HTTP Visible IP
WebRTC IPs
Proxies that don't leak
Residential IPs · SOCKS5 with remote DNS · Zero proxy headers · Elite anonymity
Understanding IP Leaks
DNS Leak
- ›DNS queries bypass the proxy tunnel
- ›Your ISP sees which domains you visit
- ›Fix: use SOCKS5 with remote DNS or a VPN
WebRTC Leak
- ›Browser WebRTC exposes local/public IPs
- ›Bypasses HTTP proxy configuration
- ›Fix: disable WebRTC or use browser extension
Frequently Asked Questions
What is a DNS leak?›
A DNS leak occurs when your DNS queries (the process of translating domain names to IP addresses) are sent outside your proxy or VPN tunnel — typically to your ISP's DNS server. This reveals which websites you're visiting even if your IP is hidden.
What is a WebRTC IP leak?›
WebRTC is a browser technology for peer-to-peer communication. It can expose your real local and public IP addresses even when using a proxy or VPN — because it uses ICE candidates that bypass the HTTP proxy tunnel.
How do I fix a WebRTC leak?›
In Firefox: set media.peerconnection.enabled to false in about:config. In Chrome: use an extension like "WebRTC Leak Prevent" or disable WebRTC via a flag. In Brave: use the built-in WebRTC leak protection setting.
Do proxies protect against DNS leaks?›
HTTP/SOCKS proxies do NOT protect against DNS leaks by default — your browser still resolves DNS using your system or ISP resolver. Only proxies with built-in DNS handling (like SOCKS5 with remote DNS) or VPNs that tunnel DNS traffic prevent leaks.
What does "reverse DNS" show?›
Reverse DNS (rDNS) maps an IP address back to a hostname. It's often set by ISPs and hosting providers and can reveal the owner of an IP even if the IP itself is unfamiliar.