Free tool
WebRTC leak test
WebRTC lets browsers make video calls directly. To do that, it can tell a website about your network addresses, sometimes including your real IP behind a VPN.
This test asks your browser for its WebRTC network candidates, the way a video-call site would, and compares any IP addresses in them with the public IP our server sees.
What WebRTC is
WebRTC (Web Real-Time Communication) is a browser standard for live audio, video and data between two people, used by many video-call and file-sharing sites. To connect two devices directly, the browser gathers "candidates": the network addresses it might be reached at. One way it learns its public address is by asking a STUN server, a small service that replies with the address it saw.
How a WebRTC leak happens
A web page can start this gathering with a few lines of JavaScript, without a camera or microphone prompt, and read the addresses the browser finds. If your VPN or browser doesn't route these requests through the tunnel, the page can learn your real public IP address while the rest of your browsing shows the VPN's.
Modern browsers hide your local network address behind a random name ending in .local (mDNS) by default, which the test reports as "hidden". That protects your local address but doesn't decide what happens to your public one.
Reading your result
| Result | What it means |
|---|---|
| No leak found | WebRTC showed no public address other than the one our server sees. |
| Local IP visible | Your private network address (such as 192.168.x.x) was exposed. It doesn't identify you on the internet, but it adds detail to a browser fingerprint. |
| Possible leak | WebRTC revealed a public address our server didn't see. If your VPN is on, this is likely your real IP. |
How to stop WebRTC leaks
- Use your VPN's app, not only a browser extension A system-wide VPN app routes the browser's WebRTC traffic through the tunnel. Many browser extensions are proxies that only cover normal page requests. Check the provider's documentation for WebRTC protection.
- Turn on your VPN's leak protection and kill switch See our guide to the kill switch.
- Limit WebRTC in the browser Firefox lets you turn WebRTC off entirely (media.peerconnection.enabled in about:config), which also stops video calls in the browser. Brave has a WebRTC IP handling setting under privacy. Chrome needs an extension to restrict it.
- Test again Run this test with the VPN on and compare it with the result from What's my IP.
Questions people ask
Do I need to fix a local IP showing?
It isn't a serious risk. Your local address is shared by millions of home networks and doesn't identify you. Hiding it removes one detail from your browser fingerprint.
Why does the test find no addresses at all?
Your browser may have WebRTC turned off, or an extension or privacy setting may block candidate gathering. That also prevents this kind of leak.
Does WebRTC leak on phones?
It can, in any browser that supports WebRTC. A system-wide VPN app on your phone routes this traffic through the tunnel too, so run the test with your VPN on.
Sources
- W3C: WebRTC 1.0, Real-Time Communication Between Browsers (w3.org) · read November 13, 2026
- IETF RFC 8445: Interactive Connectivity Establishment (ICE) (datatracker.ietf.org) · read November 13, 2026
- IETF draft: mDNS ICE candidates (hiding local addresses) (datatracker.ietf.org) · read November 13, 2026
- IETF RFC 8828: WebRTC IP Address Handling Requirements (datatracker.ietf.org) · read November 13, 2026