WebRTC Leak Test
Run a passive, in-browser WebRTC probe and compare the public IP it exposes with your HTTP public IP to detect extra IP exposure outside your VPN or proxy tunnel.
Related guides and checks
Back to IP lookupHow to Check if Your VPN Is WorkingHow to Check DNS LeaksHow to Hide Your IP AddressIP Address and Online PrivacyWhat this test observes
WebRTC is a browser feature used for voice and video calls. To connect two browsers directly, it can discover which public IP address your device uses — and that discovery does not always respect your VPN or proxy, because WebRTC traffic bypasses browser proxy settings.
This page runs a passive, in-browser observation: it collects the ICE candidates your browser would expose to any website using the same API, compares the public IP found there with your HTTP public IP, and reports whether extra public IP exposure was detected. Nothing is uploaded, and nothing is sent to the STUN server beyond the probe itself.
Best use cases
- Verifying that your VPN really covers WebRTC traffic, not just ordinary web traffic.
- Checking whether a browser proxy hides your IP — WebRTC usually bypasses it.
- Confirming that a WebRTC-blocking extension or policy is still effective.
- Collecting evidence when reporting a leak to your VPN provider.
WebRTC Leak Test
Runs a passive, in-browser probe that compares the public IP exposed by WebRTC with the IP your regular web traffic already shows, to check for extra public IP exposure.
How to fix a WebRTC leak
Stay protected
Featured PartnersBrowser-level proxies cannot stop a WebRTC leak: WebRTC traffic bypasses browser proxy settings. Use a VPN with WebRTC leak protection (a system-level tunnel that also captures UDP traffic), or disable WebRTC in the browser, then rerun the test.
Recommended fix steps
- Reconnect your VPN with leak protection enabled: a system-level (TUN) tunnel routes WebRTC UDP traffic through the encrypted tunnel.
- If you do not need browser voice or video calls, disable WebRTC with a browser extension or browser settings and the exposure disappears.
- Rerun this test and confirm the WebRTC public IP now matches your HTTP public IP.
No extra public IP exposure was found in this run. If you also want to hide your IP address or rotate your exit identity — for example keeping separate identities for different accounts — these vetted services cover both needs.
How this test works
This is a passive observation: the test opens a temporary RTCPeerConnection to a public Google STUN server (stun:stun.l.google.com:19302) and collects the ICE candidates your browser would also expose to any website using the same API. Host candidates reveal local network interfaces; server-reflexive (srflx) candidates reveal the public IP your connection presents to the internet.
This test runs entirely in your browser, starts only when you click the button, and captures no audio or video. Results are never uploaded or logged.
How to prevent WebRTC leaks
- Prefer a VPN with built-in WebRTC leak protection: a system-level (TUN) tunnel also captures the UDP traffic that browser proxies cannot.
- If you do not use browser voice or video calls, disable WebRTC entirely — via browser settings, an extension, or an enterprise policy — and the exposure disappears.
- Keep the browser updated: modern browsers hide local IPs behind mDNS hostnames, which already limits local-network exposure.
- After every configuration change, rerun the test and confirm the WebRTC public IP matches your HTTP public IP.
How to read the result
- The test is a passive observation of what your browser would expose to any website — it does not make you more visible than a normal WebRTC-using page would.
- Local (private) addresses can reveal your network segment, but they cannot geolocate you on the internet.
- A "Not detected" WebRTC IP usually means WebRTC is blocked or mDNS-protected, which is a safe state, not an error.
- A differing public IP matters most when a VPN or proxy is active: websites could learn a second address your tunnel does not cover.
WebRTC leak test FAQ
What exactly is a WebRTC leak?
WebRTC can expose a public IP address that differs from the IP your web traffic normally shows — typically your ISP address outside the VPN or proxy tunnel. Any website running JavaScript can trigger the same discovery in the background.
Why can a proxy not fix a WebRTC leak?
Browser proxies only route HTTP(S) traffic. WebRTC uses UDP and can connect directly, so it bypasses the proxy. Only a system-level tunnel (a VPN in TUN mode with leak protection) or disabling WebRTC reliably stops the exposure.
Does running this test expose my IP to anyone?
No results leave your browser. The only external party involved is the public STUN server the probe queries — the same kind of server any video-call website uses — and this site never uploads or logs your results.
The WebRTC IP shows "Not detected". Is that bad?
No. It usually means WebRTC is disabled, blocked by an extension, or your browser hides candidates behind mDNS hostnames. These are all acceptable states; the test simply has nothing to compare.
Does "no extra public IP found" guarantee full anonymity?
No. This test only observes the WebRTC channel in one run. DNS leaks, browser fingerprinting, cookies, and logged-in accounts can still identify you. Treat it as one signal among several.