WebRTC Leak Test
WebRTC is a browser feature that enables video calls and file sharing – but it can also leak your real IP address, even when you’re connected to a VPN. This test detects whether your browser is exposing IP addresses through WebRTC that don’t match your VPN connection.
Connect your VPN, then run the test below. Results appear in about 10 seconds.
Is Your VPN Actually Working?
Most VPN leak tests only check your IP. We test 3 attack vectors.
Free · No signup · Works instantly
Detecting your IP address...
IP Address
IPv6 Address
Location
Network Provider
DNS Leak Test
WebRTC Leak Test
Technical Details
What this test cannot detect
- Whether your VPN provider logs traffic
- Leaks from apps outside your browser
- VPN speed or server performance
- Malware or tracking in your VPN app
Scan this QR code to test your phone's VPN
Test could not complete
Something went wrong. Please check your internet connection and try again.
What Is a WebRTC Leak?
WebRTC (Web Real-Time Communication) is built into every major browser – Chrome, Firefox, Edge, Safari, and Opera. It powers video calls, voice chat, and peer-to-peer file sharing without requiring plugins. To establish these connections, WebRTC needs to discover your device’s IP addresses, including ones behind NATs and firewalls.
The problem: WebRTC uses STUN (Session Traversal Utilities for NAT) servers to discover your IP addresses, and this process can bypass your VPN tunnel entirely. Your browser may reveal your real public IP address to any website that runs a simple JavaScript snippet – even if your VPN is working perfectly for all other traffic.
Why WebRTC Leaks Are Different from Other VPN Leaks
Unlike DNS or IP leaks, WebRTC leaks happen at the browser level, not the network level. Your VPN can encrypt all your traffic, route all DNS through its servers, and completely hide your IP – but if WebRTC is enabled, a website can still discover your real IP through a STUN request that never touches your VPN tunnel.
This makes WebRTC leaks particularly dangerous because most users never know they’re happening. The leak is invisible – no warning, no notification, no connection drop.
Which Browsers Are Affected?
| Browser | WebRTC Enabled by Default | Can Be Disabled |
|---|---|---|
| Chrome | Yes | Via extension only (no native setting) |
| Firefox | Yes | Yes – via about:config |
| Edge | Yes | Via extension only |
| Safari | Yes (limited) | Yes – Develop menu > Experimental Features |
| Opera | Yes | Via extension or settings |
| Brave | Yes | Yes – Settings > Privacy > WebRTC IP Handling Policy |
How to Disable WebRTC
Firefox
- Type
about:configin the address bar and press Enter - Accept the risk warning
- Search for
media.peerconnection.enabled - Double-click to set the value to false
This completely disables WebRTC. Video calls on sites like Google Meet and Zoom’s web client will stop working – you’ll need their desktop apps instead.
Chrome
Chrome has no built-in setting to disable WebRTC. Your options:
- Use a VPN with WebRTC leak protection – the VPN’s browser extension blocks WebRTC from revealing your real IP while keeping WebRTC functional for video calls
- Install a WebRTC blocker extension – “WebRTC Leak Prevent” or similar extensions can restrict WebRTC to only use your VPN’s IP
Edge
Like Chrome, Edge doesn’t have a native WebRTC disable toggle. Use a VPN browser extension with WebRTC leak protection, or install a WebRTC control extension from the Edge Add-ons store.
Safari
- Open Safari > Settings > Advanced
- Check “Show features for web developers”
- Go to Develop menu > Experimental Features
- Uncheck “WebRTC mDNS ICE candidates”
Safari’s WebRTC implementation is more restrictive than Chrome or Firefox by default, making leaks less common but not impossible.
Brave
- Go to Settings > Privacy and security
- Find “WebRTC IP handling policy”
- Set to “Disable non-proxied UDP“
Brave also blocks WebRTC leaks when its built-in Shields are enabled.
How This Test Works
Our test creates a WebRTC peer connection in your browser using Google’s public STUN server. This triggers the ICE candidate gathering process, which reveals all IP addresses your browser can discover – including ones behind your VPN.
We collect these IP addresses and compare them against your detected VPN IP. If we find a public IP address that doesn’t match your VPN server, it means WebRTC is leaking your real location. Private/local addresses (like 192.168.x.x) are expected and not considered leaks.
For full details on our testing methodology, see our methodology page.
Frequently Asked Questions
Will disabling WebRTC break video calls?
Yes – fully disabling WebRTC will prevent browser-based video calls (Google Meet, Zoom web, Discord web). If you need video calls, use a VPN with WebRTC leak protection instead of disabling WebRTC entirely. This keeps video calls working while preventing IP leaks.
My VPN says it has WebRTC leak protection. Should I still test?
Yes. WebRTC leak protection varies by VPN provider. Some only protect in their browser extension (not the desktop app). Some protect in Chrome but not Firefox. Test with your actual setup – the specific browser, VPN app, and VPN server you normally use.
The test found only private IP addresses. Is that a leak?
No. Private addresses (starting with 10., 172.16-31., or 192.168.) are local network addresses that don’t reveal your identity or location. They’re expected in WebRTC and are not a privacy concern.
Does WebRTC leak through mobile browsers too?
Yes. Chrome and Firefox on Android support WebRTC and can leak. Safari on iOS has more restrictive WebRTC behavior, but leaks are still possible. Test your mobile browser separately – results can differ from desktop.
Related Tests
WebRTC is just one way your VPN can leak. For a complete privacy check, also run:
- Full VPN Leak Test – checks IP, DNS, and WebRTC in one pass
- DNS Leak Test – detects DNS queries leaking outside your VPN tunnel
- IP Leak Test – verifies your real IP address is hidden
ISPs in the US have been caught injecting tracking supercookies into customer traffic to build advertising profiles without consent.
Source: Verizon UIDH controversy, 2014-2016