iplogs.com

WebRTC leak test

This test compares the addresses your browser reveals through WebRTC with the IPv4 and IPv6 address your connection actually uses. If WebRTC shows a public address your connection doesn't, any website can read it, and on a VPN or proxy that is usually your real one.

Your result

Testing WebRTC and your connection. This takes about four seconds.

How to read the result

  • Connection is the address our server sees for this page, over IPv4 and over IPv6 if you have it. On a VPN it should be the VPN's address.
  • WebRTC public is what a STUN server sees when your browser asks it. When it matches a connection address, nothing leaks. When it's marked Leaked, sites can see an address your normal traffic hides.
  • WebRTC local lists addresses on your own network. They don't identify you on the internet, but they shouldn't be visible either.

A leak is also what VPN detection looks for: a site that sees one address over HTTP and another over WebRTC knows the first is a relay. The full VPN check on the homepage runs this comparison along with the address checks, and the glossary entry explains the mechanism.

How to fix a WebRTC leak

First check how you connect. A VPN app that sends all of the device's traffic through the tunnel normally fixes this on its own; leaks come mostly from browser-extension VPNs and proxies, which carry web requests but not WebRTC's UDP traffic. If you use an extension, switch on its WebRTC protection setting if it has one, or use the browser setting below.

  • Firefox: open about:config and set media.peerconnection.enabled to false. This turns WebRTC off, so video calls in the browser stop working until you turn it back on.
  • Brave: Settings, Privacy and security, WebRTC IP handling policy, then choose Disable non-proxied UDP.
  • Chrome and Edge: there is no switch in the settings. Use your VPN's app rather than its extension, or an extension with a WebRTC protection option, which changes how the browser picks WebRTC addresses.

Run the test again afterwards: the WebRTC public address should either match your connection or disappear.

Questions

What is a WebRTC leak?

WebRTC lets a browser make direct voice, video and data connections. To find a route, it asks a STUN server which public address it sees, and any web page can read the answer from JavaScript. If that request bypasses your VPN or proxy, the page learns your real IP address even though your normal traffic goes through the tunnel.

Does a VPN stop WebRTC leaks?

A VPN app that routes all of the device's traffic usually does, because the STUN request goes through the tunnel too. Browser-extension VPNs and proxies are the usual source of leaks: they carry the browser's web requests but not the UDP traffic WebRTC uses, so the real address can come straight back.

Is a local IP address in the result a problem?

It doesn't reveal who you are on the internet, but it narrows down your network and adds to a browser fingerprint. Current browsers normally hide local addresses behind random .local names unless a page has camera or microphone permission.

Does this test send my addresses to iplogs.com?

The WebRTC part runs in your browser and its result stays there. The page asks iplogs.com which IPv4 and IPv6 address your connection uses, which our server sees anyway, and only checks a leaked address against our VPN and proxy data if you click Check it.