WebRTC leak test

WebRTC is a protocol used by browsers for video calls and P2P. It can reveal your real IP address even if you're using a VPN.

How to read the result

• No IP detected → your browser has WebRTC disabled or blocks the request. No leak.
• A public IP that differs from the expected one → it's likely your real IP leaking despite the VPN. Problem.
• A public IP matching your VPN IP → all good, WebRTC goes through the tunnel.
• A local IP (192.168.x.x, 10.x.x.x) → that's your internal network IP. Not a real leak, but a signal an attacker can detect.

How do I fix a WebRTC leak?

Option 1 — Use a VPN that blocks WebRTC:

• NordVPN — built-in WebRTC blocker on all apps
• ExpressVPN — WebRTC protection enabled by default
• Surfshark — browser extension with WebRTC blocking
• Proton VPN — built-in blocker on its native apps

Option 2 — Disable WebRTC manually in your browser:

• Firefox: type about:config → search media.peerconnection.enabled → set to false
• Chrome / Edge: install the WebRTC Network Limiter or uBlock Origin extension
• Safari: Preferences → Advanced → "Experimental" → disable "Remove WebRTC"

Why can WebRTC reveal my real IP?

WebRTC uses a protocol called STUN to discover your real IP address, in order to set up a direct connection between two devices. This discovery happens outside the VPN tunnel on some configurations — hence the leak.

It's one of the most common and hardest leaks to detect, because it only happens in the browser. Most decent VPNs block WebRTC natively, but it's worth verifying.

Related tools

• What is my IP? — detect your public IP
• DNS leak test — check your DNS goes through the VPN
• IPv6 leak test — check no IPv6 bypasses the VPN