WebRTC Leak Test

How WebRTC Exposes Your IP

WebRTC (Web Real-Time Communication) is a browser technology used for video calls, voice chat, and file sharing. To establish peer-to-peer connections, WebRTC needs to discover all available network interfaces on your device — including your real public IP address. This discovery process uses STUN (Session Traversal Utilities for NAT) servers and happens at the browser level, meaning it can bypass your VPN tunnel entirely.

Why This Is Dangerous with a VPN

When you connect to a VPN, your traffic is routed through an encrypted tunnel and websites see the VPN's IP address instead of yours. However, WebRTC operates outside this tunnel in many VPN configurations. A website can use a simple JavaScript call to enumerate your ICE candidates and discover your real public IP — completely defeating the purpose of using a VPN.

How to Prevent WebRTC Leaks

• Firefox: Go to about:config and set media.peerconnection.enabled to false
• Chrome: Install "WebRTC Leak Prevent" extension or use uBlock Origin's WebRTC blocking
• Safari: Go to Preferences → Advanced → Experimental Features and disable WebRTC mDNS ICE candidates
• Brave: Go to Settings → Privacy and Security → WebRTC IP Handling Policy → "Disable non-proxied UDP"
• VPN: Use a VPN like VPN XO that includes WebRTC leak protection

What IPs Does WebRTC Expose?

• Public IPs — your real internet-facing IP address (most dangerous)
• Private IPs — your local network IP (192.168.x.x, 10.x.x.x) reveals your network setup
• mDNS addresses — some browsers use .local addresses instead of real IPs (safe)

How This Test Works

This test creates a WebRTC peer connection in your browser using public STUN servers (Google, Mozilla). It then collects all ICE candidates — the network addresses WebRTC discovers for establishing connections. Each candidate contains an IP address that we extract and classify as public, private, or link-local. The entire test runs in your browser — no data is sent to our servers.