🎥 Extended WebRTC Leak Test

Is WebRTC Exposing Your Real IP?

We query 4 STUN servers simultaneously to detect public IP leaks, IPv6 exposure, and mDNS behavior - a far more thorough WebRTC test than most tools offer.

🛡
Ready to test
Click “Run Extended WebRTC Test” to begin
-
Leak Score
🌐
Visible IP (Baseline)
Your VPN exit node or real IP - used to detect if WebRTC reveals a different address
Pending ▼
Run the test to detect your visible IP address.
🚨
Public IP via WebRTC
Reflexive STUN candidates - if this differs from your VPN IP, you have a leak
Pending ▼
Run the test to check for public IP leaks via WebRTC.
📶
Local / LAN IPs
Host candidates from your local network (192.168.x.x, 10.x.x.x)
Pending ▼
Run the test to check local IP exposure.
🔢
IPv6 Leak via WebRTC
WebRTC can expose real IPv6 addresses even when your VPN handles IPv4 correctly
Pending ▼
Run the test to check for IPv6 leaks via WebRTC.
🧱
mDNS Obfuscation
Checks if Chrome/Edge replaces your LAN IP with a privacy-protecting .local mDNS hostname
Pending ▼
Run the test to check mDNS hostname behavior.
⚖️
Final Summary
Overall WebRTC leak verdict across all 4 STUN servers
Pending ▼
Run the test to see the final WebRTC summary.

What Is a WebRTC Leak?

WebRTC (Web Real-Time Communication) is used by browsers for video calls, voice chat, and peer-to-peer connections. It needs to know your real IP address to work - and it bypasses your VPN tunnel to discover it, using STUN servers. This means your real home IP can be exposed to any website running WebRTC JavaScript, even when your VPN is connected.

How to Fix WebRTC Leaks

  • Firefox: Go to about:config → set media.peerconnection.enabled to false
  • Chrome / Edge: Install “WebRTC Leak Prevent” or “uBlock Origin”
  • Brave: Settings → Privacy → WebRTC IP handling → Disable non-proxied UDP
  • VPNs with built-in protection: Mullvad, ProtonVPN, ExpressVPN block WebRTC leaks
  • Safari: Already limits WebRTC IP exposure by default