Skip to content
Free tool

WebRTC leak test

A WebRTC leak happens when your browser reveals your real IP address through WebRTC even though your traffic runs through a proxy or VPN. This free test lists every IP WebRTC exposes and compares it with the IP websites see.

IP websites see (HTTP)Testing…

The test runs in your browser. It asks public STUN servers which address your connection appears from, and compares that with the IP our server sees. Nothing is stored.

How the WebRTC leak test works

  1. 1

    Your browser gathers ICE candidates

    The page opens a WebRTC connection that never connects to anyone. To prepare it, the browser lists its network addresses (host candidates).
  2. 2

    A STUN server reports your public IP

    The browser asks a public STUN server which address its request came from (server-reflexive candidates). That is the IP WebRTC would share with a peer.
  3. 3

    We compare it with your HTTP IP

    At the same time the page reads the IP your web requests arrive from, the one shown on What Is My IP.
  4. 4

    You get a verdict

    A public WebRTC address that differs from your visible IP while a proxy is on is a leak. Hidden or matching addresses are safe.

Why WebRTC leaks matter for proxy users

Websites that score risk, such as social networks, marketplaces and ad platforms, routinely run the same WebRTC check this page does. If it returns an address that doesn't match your proxy, the session looks like someone hiding their location, and every account in that browser can be linked to your real connection.

Account linking

One leaked home IP behind ten proxied accounts ties all ten together, the fastest way to lose a multi-account setup.

Location mismatch

A US proxy IP with a WebRTC address in another country is a classic fraud signal and triggers checks or blocks.

Fingerprint detail

Even local addresses like 192.168.1.20 add entropy to your browser fingerprint and help sites recognise you.

Wasted clean IPs

A super clean proxy IP can't protect a session if the browser hands out the address behind it.

How to fix a WebRTC leak

  • Use an anti-detect browser. Tools such as Multilogin replace the WebRTC address with your proxy IP in every profile, so each account shows one consistent address.
  • Limit WebRTC with an extension. In Chrome and Edge, a WebRTC control extension can restrict WebRTC to the proxied connection or turn it off.
  • Disable WebRTC in Firefox. Open about:config and set media.peerconnection.enabled to false.
  • Proxy the whole connection. When an app or OS-level client sends all traffic, including UDP, through the proxy, STUN sees the proxy's IP.
  • Re-test after every change with this page and What Is My IP.

Frequently asked questions

WebRTC lets browsers make direct audio, video and data connections. To do that, the browser discovers its own IP addresses, and any website can ask for them with a few lines of JavaScript. If the browser finds its real public IP while your traffic goes through a proxy or VPN, the site learns the address you meant to hide. That is a WebRTC leak.

Clean, dedicated IPs for every profile

Static US ISP proxies as low as $0.75/IP, never shared, delivered instantly. Test them for $4.99.