JetproxyJetproxyTry for free

WebRTC Leak Test

Check if your real IP leaks through WebRTC

WebRTC can bypass proxies and VPNs, revealing your real IP address. This test checks all ICE candidates of your browser.

WebRTC can reveal your real public or local IP through STUN even when the site traffic itself goes through a proxy or VPN. This test shows whether your browser is leaking the network identity you were trying to hide.

How it works

  1. 1The page asks your browser for ICE candidates the same way a real site would during a WebRTC call.
  2. 2We inspect the candidates for public, relay, host, and local interface addresses.
  3. 3If the browser exposes an address outside the expected proxy path, the tool flags it as a leak.
  4. 4You can then disable WebRTC, force relay, or switch browser profiles before using the proxy in production.

What it checks

  • Public IPs returned by STUN negotiation
  • Local LAN addresses such as 192.168.x.x or 10.x.x.x
  • Proxy or TURN relay behaviour versus direct browser exposure
  • Mismatch between the IP in the page request and the IP seen via WebRTC

Frequently asked questions

Do all proxies protect against WebRTC leaks?
No. Most proxies only handle HTTP or SOCKS traffic. WebRTC is a browser-level feature and can bypass that path unless you harden the browser itself.
Is a local IP leak dangerous?
A local IP does not reveal your street address, but it adds entropy to your fingerprint and proves the browser is exposing more network data than many anti-fraud systems expect.
What should I do if I see a leak?
Disable WebRTC, use a browser that supports proxy-safe WebRTC settings, or route calls through TURN-only mode inside an anti-detect profile.

Related tools

Use this tool for