VPN Leak Test
Test whether your VPN is leaking your real IP address via WebRTC. See your detected IP addresses and check if your actual location is exposed despite an active VPN connection.
Check If Your VPN Is Leaking Your IP
A VPN leak occurs when your browser reveals your real IP address even though you're connected to a VPN. WebRTC — a browser feature for video/audio calls — can bypass the VPN tunnel and expose your true IP to any website. This test detects it.
- WebRTC leak detection: Checks all IP addresses your browser exposes via WebRTC
- Public IP vs. WebRTC IP: Compares what your VPN shows vs. what WebRTC reveals
- IPv4 and IPv6: Tests both address families — IPv6 leaks are often overlooked
- Instant results: No extension or account needed — runs in your browser tab
What Is a WebRTC VPN Leak?
- WebRTC purpose: A browser API for peer-to-peer video, audio, and data connections — used by Google Meet, Zoom web, Discord browser, and similar apps
- The leak mechanism: To establish peer connections, WebRTC uses STUN servers to discover your device's actual network interfaces — including your real public IP, even behind a VPN
- Why VPNs miss it: The WebRTC STUN request goes directly to Google/Cloudflare STUN servers, bypassing the VPN's encrypted tunnel in some configurations
- Who is at risk: Chrome and Firefox users on Windows are most affected; Safari restricts WebRTC more aggressively; mobile browsers vary
How to Fix a WebRTC VPN Leak
- Use a VPN with WebRTC leak protection: Most premium VPN clients (Mullvad, ProtonVPN, ExpressVPN) handle WebRTC leak prevention in their desktop apps — but not necessarily in the browser extension
- Firefox: Go to
about:config→ setmedia.peerconnection.enabledtofalse— disables WebRTC entirely (breaks video calls) - Chrome: Install the WebRTC Network Limiter extension (by Google) or uBlock Origin's WebRTC policy setting
- uBlock Origin: Settings → Privacy → "Prevent WebRTC from leaking local IP addresses" — recommended approach that keeps WebRTC functional for legitimate uses
Frequently Asked Questions
If the test shows two IPs, does that mean my VPN is leaking?
Not necessarily. If both IP addresses belong to your VPN provider's range, there's no leak — you're seeing two VPN-assigned IPs (common when the VPN assigns both an IPv4 and IPv6 address). A leak is confirmed when one of the detected IPs matches your ISP-assigned IP or resolves to your home location rather than the VPN server location. Compare the detected IPs against your real IP (check from a non-VPN connection) to confirm.
Does this test cover all types of VPN leaks?
This test specifically checks for WebRTC IP leaks — the most common browser-level leak. It does not test for DNS leaks (where DNS queries reveal your location despite the VPN) or IPv6 leaks outside the browser context. For DNS leak testing, use a dedicated DNS leak test tool. For comprehensive VPN auditing, run both tests with your VPN active.
Should I disable WebRTC entirely?
Disabling WebRTC stops all browser-based video/audio calls — Google Meet, Zoom web, Discord in browser, and similar apps won't work. A better approach is using uBlock Origin's WebRTC leak prevention, which prevents local IP exposure while keeping WebRTC functional for legitimate peer-to-peer communication. Only disable WebRTC entirely if you never use browser-based video calls and prioritize privacy over functionality.