WebRTC Leak Test - Does Your Browser Reveal Your IP?
WebRTC leak test
WebRTC lets browsers make direct audio, video and data connections. To do that, a page can ask your browser for its network addresses – without any permission prompt. This test shows exactly what a website can learn this way.
Press the button: your browser collects its WebRTC addresses, and we compare them with the address this site sees.
Uses the STUN server stun.cloudflare.com:3478. Nothing is saved.
Addresses ending in ".local" are random names (mDNS) that modern browsers use instead of your real local IP. They change and cannot be resolved by websites, so they are not a leak.
Nothing is saved. The addresses are collected and compared in your browser; only the usual request for the IP this site sees goes to our server, and it is not logged. The STUN server sees your IP address, as any server you connect to does.
WebRTC leaks explained
Video calls in the browser need a direct path between two devices. To find one, WebRTC collects "ICE candidates": every address under which your device might be reachable. Any website can start this process in the background, which is why it matters for privacy – especially if you rely on a VPN.
How the test works
- 1 When you press the button, the page opens a WebRTC connection that is never actually used for a call and lets your browser gather its candidates, asking the STUN server for your public address.
- 2 At the same time, our server reports the address your normal web traffic comes from – with a VPN on, that should be the VPN’s address.
- 3 The two are compared. A public WebRTC address that differs from the one this site sees, or a raw local address, is pointed out; hidden ".local" names are shown as such.
What is a WebRTC leak?
A VPN routes your web traffic through its own server, so websites see the VPN’s address. WebRTC’s STUN requests are a separate kind of traffic, though. If the VPN app does not capture them – for example because it only covers IPv4, uses split tunneling or is a browser extension acting as a proxy – the STUN server sees your real address, and the page can read it from the candidate list.
Candidate types: host, srflx and relay
A host candidate is an address of your device itself – today usually hidden behind a ".local" name. A server-reflexive (srflx) candidate is the public address the STUN server saw your request come from; this is the one that can expose your real IP. A relay candidate belongs to a TURN relay server and only appears when the page configures one; this test does not.
Why the result depends on your setup
Without a VPN, a "different public IP" is rare; the WebRTC address and the site address normally match. On a dual-stack connection you may see one IPv4 and one IPv6 address – that is expected. Some company networks and mobile operators route traffic differently, so a single result is a hint, not proof. Run the test with the VPN on and off and compare.
How to prevent WebRTC leaks
Use a VPN app that tunnels all system traffic, including UDP and IPv6, rather than a browser-only proxy, and turn on its leak protection if it has one. Many browsers also have a setting or policy that limits WebRTC to the proxied connection or turns it off entirely – note that turning it off breaks video calls in the browser. Afterwards, run this test again.