Is your browser leaking your IP?
Even with a VPN active, your browser's WebRTC stack can expose your real IP. This test runs locally on your device and finishes in seconds.
Takes about 3 seconds · No data leaves your device
IP addresses exposed
Compare these to your real IP from scanmyipaddress.com to spot the leak.
No IPs detected yet. Click "Start leak test" above.
About WebRTC leaks
WebRTC is the technology that powers video calls in your browser — Google Meet, Discord, Zoom Web, and many others. To establish peer-to-peer connections efficiently, WebRTC needs to know your network's IP addresses.
The problem: any website can quietly ask your browser for these IPs, even without you using video calls. This works around most VPNs because the IPs are gathered by your local network stack before VPN tunneling takes effect.
If this test shows your real public IP while you're connected to a VPN, that's a confirmed WebRTC leak.
Learn about VPNs that block WebRTC leaksHow to fix WebRTC leaks
-
Use NordVPN (recommended) Built-in WebRTC leak protection, audited no-logs policy→
-
Install a browser extension uBlock Origin or WebRTC Network Limiter→
-
Disable WebRTC in Firefox about:config → media.peerconnection.enabled = false→
-
Switch to Safari Most restrictive WebRTC implementation→
Frequently asked questions
What is a WebRTC leak?
A WebRTC leak happens when your browser's WebRTC stack reveals your real IP address even though you're connected to a VPN. WebRTC is designed for peer-to-peer video and voice calls, and to make those connections work, your browser may share your local network IPs with any website that asks — bypassing your VPN entirely.
How do I fix a WebRTC leak?
Three main approaches: (1) Use a browser extension like uBlock Origin or WebRTC Network Limiter that blocks WebRTC, (2) Use a VPN with built-in WebRTC leak protection (most paid VPNs offer this), or (3) Disable WebRTC in your browser settings — possible in Firefox, requires an extension in Chrome.
Is a WebRTC leak dangerous?
For most users, it's more a privacy concern than a security one. The leak exposes your real public IP and local network IPs to websites that explicitly check for them. This defeats the privacy purpose of using a VPN, but doesn't directly give attackers access to your device.
Do all browsers have WebRTC leaks?
Chrome, Edge, Brave, and Opera all support WebRTC by default and can leak IPs. Firefox supports WebRTC but has settings to limit leakage. Safari has the most restrictive implementation and leaks the least. Mobile browsers vary by platform.
Does this test send data anywhere?
No. The WebRTC leak test runs entirely in your browser using local JavaScript. No IPs detected by the test are sent to our servers or any third party. We only see what your browser sends in a normal page request (your public IP, same as any website).
What if the test shows nothing?
That's good news! Either your browser doesn't support WebRTC, has it disabled, or has WebRTC leak protection active. You're not leaking via this vector.