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

  1. 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.
  2. 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.
  3. 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:

ICE Candidate Types: host (Local Interface) • srflx (STUN Reflexive / Public NAT) • relay (TURN)
DNS-over-HTTPS (DoH): Encrypted HTTPS JSON/DNS query to resolver endpoints

Helpful Tips for Preventing IP & DNS Leaks

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.

IP & DNS Leak Terminology, ICE Types & Reference Table (16 Rows)

Use this reference table to interpret WebRTC ICE candidates, DNS concepts, and network diagnostics.

Term / Check Type / Standard What It Indicates Notes
ICE host Candidate Local interface / mDNS Local LAN address or .local ID Browsers often mask with mDNS
ICE srflx Candidate Server-reflexive (STUN) External/NAT address seen by STUN Reveals public path if unrouted
ICE relay Candidate TURN relay Relayed media candidate Used behind strict NAT/firewalls
DNS Leak Resolver routing check DNS queries bypass VPN/intended path Can expose browsing queries to ISP
DNS-over-HTTPS (DoH) DNS over HTTPS (port 443) Encrypts DNS lookups in transit Prevents on-path DNS snooping
DNS-over-TLS (DoT) DNS over TLS (port 853) Encrypted transport DNS protocol Common on OS/router resolvers
RFC1918 Private IPv4 10/8, 172.16/12, 192.168/16 Private home/office LAN address Not routable on public internet
IPv6 Link-Local fe80::/10 Local subnet IPv6 address Scoped to local link only
Global Privacy Control navigator.globalPrivacyControl Browser opt-out signal true when enabled by user/ext
Do Not Track (DNT) navigator.doNotTrack Legacy tracking preference flag 1 = enabled, else unset
Network Info API navigator.connection Effective connection type & speed Available in supported browsers
Copy & Download Report .txt / Clipboard Exports full leak & DoH snapshot Local plain-text output
Client-Side Engine Browser WebRTC ICE & Fetch DoH Diagnostics — Zero Server Latency
Server Uploads None — Your diagnostic results are generated locally without server logging
Privacy Status 100% Local Inspection — Zero personal identifiers stored
No Sign-Up Required Instant browser network check with zero registration

Inspecting your browser fingerprint, looking up MAC addresses, testing password strength, or formatting JSON? Explore our companion client-side tools:

Frequently Asked Questions

It creates a temporary local RTCPeerConnection with public STUN servers to gather ICE candidate strings—identifying whether local/private or reflexive/public IP candidates are exposed in your browser session—and immediately closes the peer connection.
Some corporate firewalls, captive portals, or ad/tracker blockers restrict direct browser fetch() calls to external DoH endpoints—when that happens, the tool reports that endpoint as blocked/unreachable rather than crashing.
No. All diagnostic aggregation and report exports happen inside your browser without storing or logging your report on any server.
Yes! It is completely free with no sign-up required.