Privacy tool

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.

What 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.

Not tested
HTTP public IP—
WebRTC public IP—
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

  1. Prefer a VPN with built-in WebRTC leak protection: a system-level (TUN) tunnel also captures the UDP traffic that browser proxies cannot.
  2. 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.
  3. Keep the browser updated: modern browsers hide local IPs behind mDNS hostnames, which already limits local-network exposure.
  4. 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