Complete User Guide to IP Leaks, WebRTC ICE Candidates & DNS Leak Testing
How IP Address Leaks and DNS Leaks Happen on Connections and VPNs
When you browse the web—especially over a VPN, proxy, or corporate network—two subtle leakage vectors can reveal more about your network path than you expect: WebRTC IP leaks and DNS leaks. WebRTC (Real-Time Communication) uses Interactive Connectivity Establishment (ICE) candidates—host (local LAN address), srflx (server-reflexive public/NAT address discovered via STUN), and relay (TURN)—which in unhardened browsers can expose local RFC1918 addresses (such as 192.168.x.x or 10.x.x.x) or an unencrypted IP if tunnel routing misbehaves. Meanwhile, a DNS leak occurs when domain-name queries are resolved by your ISP's default DNS server outside your VPN tunnel rather than through an encrypted or tunnel-routed resolver (such as DNS-over-HTTPS / DoH). A browser-based IP & DNS Leak Test inspects WebRTC ICE candidates and runs DoH queries directly from your browser—with zero server uploads.
How to Run an IP & DNS Leak Check in 3 Easy Steps
- Connect to Your Network or VPN & Click Run Check: Click Run IP & DNS Leak Check to gather WebRTC ICE candidates, network connection telemetry, and DNS-over-HTTPS query responses.
- Inspect WebRTC Candidates & DoH Resolvers: Check whether any unexpected local or reflexive IP addresses appear in WebRTC candidates and verify which DoH resolvers respond cleanly.
- Export Your Diagnostic Report: Save a copy of your network diagnostic snapshot via Copy Diagnostic Report or Download .txt.
WebRTC ICE Candidate Types & DNS Resolution
Understanding ICE candidate tags helps distinguish local LAN addresses from external NAT/public addresses:
DNS-over-HTTPS (DoH): Encrypted HTTPS JSON/DNS query to resolver endpoints
Helpful Tips for Preventing IP & DNS Leaks
- Enable VPN Kill Switch & DNS Leak Protection: If using a VPN, enable its built-in kill switch and ensure DNS queries are routed through the VPN tunnel or trusted DoH/DoT resolvers.
- Check Browser WebRTC & Secure DNS Settings: Modern browsers often use mDNS hostnames (
.local) to hide raw LAN IPs and let you configure Secure DNS (DoH) directly in browser privacy settings. - Compare Before and After Toggling Your VPN: Running a check before and after connecting your VPN clearly highlights changes in reflexive/public routing and resolver behavior.
Worked Example: When connected to a properly configured VPN with encrypted DNS active, WebRTC reflexive candidates reflect the VPN exit endpoint rather than your home ISP IP, and DNS-over-HTTPS probes return valid A records without routing unencrypted queries to an unintended ISP resolver.