By: Katia Belokon · Updated November 2026
What is WebRTC?
WebRTC (Web Real-Time Communication) is an open standard that allows browsers to establish peer-to-peer connections directly — without a server in the middle — for video calls, voice calls, file sharing, and other real-time applications. It is built into all major browsers: Chrome, Firefox, Safari, Edge, and Brave.
To establish a peer-to-peer connection, WebRTC uses a process called ICE (Interactive Connectivity Establishment). ICE collects a list of "candidates" — network addresses that each peer can use to connect. These candidates include your local network IP (e.g., 192.168.1.x), your public ISP IP, and sometimes addresses from STUN servers that help peers locate each other through NAT.
What is a WebRTC IP leak?
A WebRTC leak occurs when a website uses the browser's WebRTC API to collect your ICE candidates and one of them shows a public IP address other than your VPN's, usually your ISP address. WebRTC traffic follows the device's normal routing (RFC 8828), so a VPN app that tunnels all traffic carries it too, and the only public address a site sees is the VPN's. Leaks come from setups where some traffic skips the tunnel: a browser-extension VPN that proxies only web pages, split tunnelling, an IPv6 route left outside the tunnel, or a tunnel that dropped.
The leak typically exposes two types of addresses:
- Local IP: Your internal network address (e.g., 192.168.1.100). This reveals your home or office network configuration to any website that queries WebRTC.
- Public IP: Your real ISP-assigned public IP address, distinct from the VPN exit IP. Any website can read this via a simple JavaScript snippet without any user interaction or permission.
Why VPNs do not block WebRTC leaks by default
VPN clients route traffic at the operating system network layer — they intercept IP packets and redirect them through the encrypted tunnel. WebRTC's ICE candidate collection works differently: the browser's internal APIs query the OS for network interface addresses and communicate those addresses within the WebRTC protocol negotiation, rather than sending them as regular IP packets that the VPN can intercept.
The result is that the VPN can successfully mask your IP for all normal browsing and requests, while simultaneously the browser can read and expose your real IP address to any site that calls the WebRTC API. The two systems operate independently.
How to test for a WebRTC leak
- Without your VPN connected, run MyIPScan's WebRTC Leak Test. Note your real public IP shown in the WebRTC candidates section — this is your baseline.
- Connect your VPN.
- Run the WebRTC Leak Test again in the same browser session.
- If you see your real ISP public IP in the WebRTC candidates alongside (or instead of) the VPN IP, you have a WebRTC leak.
Note: Seeing a local IP (192.168.x.x or 10.x.x.x) in WebRTC candidates is normal and does not reveal your public identity. The concern is if your real public IP — the one your ISP assigned — appears alongside or instead of the VPN IP.
How to disable or restrict WebRTC
The approach depends on your browser:
- Firefox: In the address bar, type
about:config, search formedia.peerconnection.enabled, and set it tofalse. This fully disables WebRTC. - Chrome / Edge: The reliable fix is a VPN app that tunnels all traffic, not a browser extension. Chrome no longer runs uBlock Origin (Manifest V2 extensions were switched off in 2025), and uBlock Origin Lite has no WebRTC setting. Google's WebRTC Network Limiter extension can limit WebRTC to the default public route.
- Brave: Go to Settings → Privacy and security → WebRTC IP handling policy and select "Disable non-proxied UDP." Brave offers this natively without extensions.
- Safari: Safari does not block WebRTC. Unless a site has camera or microphone permission, it hides your local addresses but still shares the public address a STUN server sees, so whether that is your VPN's address or your ISP's depends on the VPN, not on Safari. Safari has no switch to turn WebRTC off; test it with the VPN on.
- VPN browser extensions: Most reputable VPN providers' browser extensions include a WebRTC IP leak prevention option. Enable it in the extension settings.
How to interpret WebRTC leak test results
| Result | Usually means | What to check next |
|---|---|---|
| Only VPN or expected route appears | WebRTC candidates match the route you intended | Still check DNS, IPv6, and browser fingerprinting |
| Local private address or mDNS name appears | Browser is exposing or masking local candidate information | Check browser privacy settings and whether local exposure matters for your threat model |
| ISP public IP appears while VPN is active | Possible route mismatch or VPN leak protection gap | Enable VPN leak protection, reconnect, and retest |
| IPv6 candidate appears unexpectedly | IPv6 may not follow the expected VPN or proxy route | Check VPN IPv6 support or documented IPv6 blocking behavior |
| Different browsers show different results | Browser-specific WebRTC, extension, policy, or profile behavior | Test the browser you actually use for sensitive activity |
| No candidates appear | WebRTC may be blocked, limited, or unavailable in that browser/session | Confirm whether calls or real-time apps still work if needed |
WebRTC leak vs DNS leak vs VPN leak
| Check | What it inspects | Common mismatch | Best next step |
|---|---|---|---|
| WebRTC leak | Browser network candidates | Candidate reveals unexpected local, public, VPN, proxy, or IPv6 signal | Adjust browser, VPN, WebRTC, or firewall behavior |
| DNS leak | Resolver path and domain lookup route | DNS goes to ISP, router, or browser DoH provider instead of expected DNS | Align VPN DNS, browser DNS, system DNS, and router DNS |
| VPN leak | Combined IP, DNS, WebRTC, IPv6, and browser signals | One signal follows a different route from the VPN expectation | Test each layer separately, then fix the route mismatch |
These checks overlap, but they are not interchangeable. A clean DNS result does not prove WebRTC is clean. A clean WebRTC result does not prove DNS or IPv6 is clean.
When WebRTC leaks matter most
- VPN or proxy use: candidates that differ from the expected route can reduce confidence in the setup.
- Public Wi-Fi: local network and browser signals may reveal more context than expected.
- Travel: changing networks, VPN exits, and IPv6 behavior can make results inconsistent.
- Work or school devices: managed policies may control WebRTC, VPN, and DNS behavior.
- Sensitive accounts: account providers may evaluate IP, region, device, browser, and behavior signals together.
- Browser fingerprinting review: WebRTC candidates can be one signal among many browser attributes.
Frequently asked questions
What is a WebRTC leak?
A WebRTC leak is when the browser's WebRTC API shows a website a public IP address other than your VPN's, usually your ISP address. Current browsers hide local network addresses behind random .local (mDNS) names, so seeing those is normal, not a leak.
Why do VPNs not block WebRTC leaks by default?
A VPN app that tunnels all traffic does cover WebRTC: the browser sends WebRTC requests through the operating system like any other traffic, so they leave through the tunnel. Leaks happen when the VPN does not carry everything: a browser-extension VPN that proxies only web pages, split tunnelling, IPv6 left outside the tunnel, or a dropped tunnel.
How do I test for a WebRTC leak?
Connect your VPN, then run MyIPScan's WebRTC Leak Test. If your real ISP public IP appears in the WebRTC candidates alongside or instead of the VPN IP, you have a leak. Establish a baseline by running the test without a VPN first.
How do I disable WebRTC in my browser?
Firefox: set media.peerconnection.ice.default_address_only to true in about:config, or media.peerconnection.enabled to false to switch WebRTC off. Brave: set WebRTC IP handling policy to "Disable non-proxied UDP" in Privacy settings. Chrome/Edge: use a VPN app that tunnels all traffic; Google's WebRTC Network Limiter extension can limit WebRTC to the default route. Switching WebRTC off can break video calls.
Does WebRTC only leak IPs when using a VPN?
Without a VPN, WebRTC shows the same public IP the website already sees, so nothing new is exposed, and current browsers hide local network addresses behind random .local names. It matters with a VPN: a WebRTC address other than the VPN's means some traffic is leaving outside the tunnel.