Test Your Browser for WebRTC Leaks
Find out if your browser is leaking your true identity. See if WebRTC is bypassing your VPN right now.
Running WebRTC leak test...
Understanding Your Test Result
Below you can see all possible statuses the WebRTC Leak test may display, ordered from best to worst protection.
Possible statuses (from best to worst protection)
No Leak (WebRTC Disabled) WebRTC is Disabled – Maximum Privacy.
No Leak (VPN Protected) VPN Protected – No IP Leaks Detected. WebRTC is Properly Restricted for Ultimate Security.
No Leak (Protected) Secure – No Public IP Addresses Exposed via WebRTC.
No Leak (VPN Working) Protected – WebRTC is Only Showing Your VPN IP. Your Real Identity Remains Hidden.
No Leak WebRTC shows the same IP as your public IP — no additional IPs are exposed.
No VPN Detected No VPN Detected – WebRTC is Showing Your Public IP. (Standard Browsing Mode)
LEAK DETECTED! LEAK DETECTED! – WebRTC is Exposing Your Real IP Address. Your Location and Privacy Are at Risk.
What is a WebRTC Leak?
WebRTC (Web Real-Time Communication) is a browser technology that enables video calls, voice chat, and peer-to-peer file sharing directly in the browser — without plugins. Sites like Google Meet, Discord, and Zoom use it.
To establish a direct connection between two users, WebRTC needs to know both parties' IP addresses. It does this using a protocol called ICE (Interactive Connectivity Establishment), which can discover your real IP address even if you are using a VPN.
A WebRTC leak is one of the most common ways a website can see your real IP address despite an active VPN. It bypasses the VPN entirely at the browser level — not a network level failure, but a browser-level one.
How Does This Test Work?
This test runs entirely in your browser — no data is sent to our servers:
- Your public IP address is fetched via ipify.org — this is the IP your VPN (or ISP) presents to the outside world
- An RTCPeerConnection is created using multiple STUN servers (Google, Cloudflare, Nextcloud) — this is the same mechanism websites use for WebRTC calls
- Any IPs discovered via WebRTC are compared against your public IP — a mismatch means a leak
- Private/local IPs (192.168.x.x, 10.x.x.x) are excluded — only public IPs that reveal your identity are reported
Who Is Affected?
WebRTC leaks affect Chromium-based browsers (Chrome, Edge, Brave, Opera) and Firefox by default. Safari has WebRTC restrictions that generally prevent leaks.
| Browser | Default Risk | Fix |
|---|---|---|
| Tor Browser | None | WebRTC disabled by default — no action needed |
| Brave (Tor Mode) | None | WebRTC blocked in Tor mode — no action needed |
| Mullvad Browser | None | WebRTC disabled by default — no action needed |
| LibreWolf | None | WebRTC disabled by default — no action needed |
| Brave | Low | Blocked by default — verify in Settings → Privacy and Security → WebRTC IP handling policy |
| Safari | Low | Generally not vulnerable — WebRTC does not expose local IPs |
| Firefox | High | Set media.peerconnection.enabled to false in about:config |
| Google Chrome | High | VPN with WebRTC protection, or install WebRTC Leak Prevent extension |
| Microsoft Edge | High | VPN with WebRTC protection, or install WebRTC Leak Prevent extension |
| Opera | High | VPN with WebRTC protection — Opera's built-in VPN does not block WebRTC leaks |
| Samsung Internet | High | VPN with WebRTC protection — no browser-level fix available |
How to Fix a WebRTC Leak?
- Use a VPN with a browser extension: Most leading VPN providers — including NordVPN, Surfshark, ExpressVPN, and ProtonVPN — offer browser extensions that block WebRTC leaks automatically. For maximum protection, pair your VPN with its browser extension, or choose a privacy-first browser like Mullvad Browser or Tor Browser, where WebRTC is disabled by default.
- Firefox: Go to
about:config, search formedia.peerconnection.enabled, and set it tofalsein advanced configuration — this disables WebRTC entirely - Chrome / Edge: Install a browser extension such as WebRTC Leak Prevent or uBlock Origin (with WebRTC blocking enabled in advanced settings)
- Switch to Brave: Brave blocks WebRTC IP leaks by default under Settings → Privacy and Security → WebRTC IP handling policy
- Disable WebRTC at the OS level: Some VPN clients (Mullvad) can block WebRTC system-wide regardless of browser
Note: Disabling WebRTC will break browser-based video calls (Google Meet, Zoom web, Discord). If you need both privacy and video calls, use a VPN that handles WebRTC at the client level rather than disabling WebRTC in the browser.
WebRTC and Tor
The Tor Browser disables WebRTC by default — it is one of the most effective browsers for preventing this type of leak. However, Tor routes all traffic through the Tor network, which significantly reduces browsing speed. It is not a practical solution for everyday use if you need fast, real-time communication.
The Verdict: Close the WebRTC Loophole
WebRTC leaks are silent and dangerous — websites can call a JavaScript API that bypasses your VPN entirely and reveals your home IP address without any visible indication.
The most reliable fix is a VPN that actively blocks WebRTC at the client level. The VPNs below include WebRTC leak protection and have been tested to confirm it works.
View VPNs with WebRTC Leak Protection →