WebRTC Leak Test

Checks if your browser reveals IP addresses via WebRTC.

Takes about 5 seconds

How This Test Works

  1. We create a WebRTC peer connection in your browser
  2. The browser gathers ICE (Interactive Connectivity Establishment) candidates
  3. These candidates may contain your local, private, or public IP addresses
  4. We analyze the candidates to detect any exposed IP addresses
  5. If public IPs are found while using a VPN, this indicates a WebRTC leak

Privacy note: This test runs entirely in your browser. No IP addresses are sent to our servers.

What is WebRTC?

WebRTC (Web Real-Time Communication) is a browser technology that enables direct peer-to-peer connections for video calls, voice chat, and file sharing. When you use Google Meet, Discord in your browser, or many other communication tools, WebRTC is working behind the scenes.

The technology is genuinely useful-it allows real-time communication without plugins or additional software. But there's a catch: to establish these direct connections, WebRTC needs to discover your IP addresses, including your real public IP.

Why WebRTC bypasses VPNs

Here's the problem: WebRTC operates at the browser level, not the network level. When your browser gathers "ICE candidates" (potential connection paths), it queries your network interfaces directly. This happens through a mechanism called STUN (Session Traversal Utilities for NAT), which is designed to discover your public IP address.

Even if all your regular internet traffic flows through a VPN, WebRTC can still reach out to STUN servers and discover your real IP. The VPN encrypts your traffic, but it can't stop your browser from asking "what's my real IP?" through WebRTC.

What websites can see

Any website can use JavaScript to trigger WebRTC and potentially discover:

  • Your real public IP address (even behind a VPN)
  • Your local/private IP addresses (like 192.168.x.x)
  • Information about your network configuration

Why WebRTC Leaks Are Dangerous

WebRTC leaks are particularly insidious because they're silent and invisible. You won't see any warning, and your VPN will appear to be working normally. Meanwhile, websites can quietly discover your real identity.

VPN bypass

Your real IP is exposed even when connected to a VPN, completely defeating the purpose of using one for privacy.

Location revealed

Your real geographic location can be determined from your public IP, even if your VPN shows you in another country.

Enhanced fingerprinting

Local IP addresses can be combined with other browser data to create a more unique fingerprint for tracking.

Silent exposure

No visible indication that your IP is being leaked-you'd never know without running a test like this one.

How to Disable WebRTC (Browser Guide)

The fix depends on which browser you use. Here's how to disable or limit WebRTC in each major browser:

Firefox allows you to completely disable WebRTC:

  1. Type about:config in the address bar and press Enter
  2. Click "Accept the Risk and Continue"
  3. Search for media.peerconnection.enabled
  4. Double-click to set it to false

Note: This will break video calling features in your browser. You can re-enable it when needed.

Chrome doesn't allow disabling WebRTC directly. You have two options:

Option 1: Use an extension

  • WebRTC Leak Prevent - Blocks WebRTC IP leaks
  • uBlock Origin - Enable "Prevent WebRTC from leaking local IP addresses" in settings

Option 2: Use a VPN with WebRTC protection

Many premium VPNs include browser extensions that block WebRTC leaks automatically.

Brave has built-in WebRTC controls:

  1. Go to Settings → Privacy and security
  2. Find WebRTC IP Handling Policy
  3. Select "Disable non-proxied UDP"

This prevents WebRTC from revealing your real IP while still allowing WebRTC to function through proxies/VPNs.

Safari has limited WebRTC exposure by default. To further restrict it:

  1. Go to Safari → Preferences → Advanced
  2. Enable "Show Develop menu in menu bar"
  3. Go to Develop → Experimental Features
  4. Look for WebRTC-related options and disable as needed

Safari generally handles WebRTC more privately than Chrome, but using a VPN with leak protection is still recommended.

Android:

  • Use Firefox and disable WebRTC via about:config (same as desktop)
  • Use Brave with WebRTC policy set to disable non-proxied UDP
  • Chrome on Android has no built-in WebRTC controls

iOS:

  • Safari on iOS has limited WebRTC exposure
  • Use a VPN app with WebRTC leak protection
  • Consider using Brave browser for better privacy controls

WebRTC Leak FAQ

Yes, completely disabling WebRTC will break browser-based video calling (Google Meet, Discord web, etc.). However, you have options: use the "Disable non-proxied UDP" setting in Brave (which allows WebRTC through VPNs), or temporarily re-enable WebRTC when you need video calls. Dedicated apps like Zoom or Skype desktop clients don't rely on browser WebRTC.

Local/private IPs are less concerning than public IPs because they don't directly identify you on the internet. However, they can still be used for:

  • Browser fingerprinting - Your local IP pattern can be combined with other data to track you
  • Network reconnaissance - Reveals information about your network setup

Modern browsers increasingly mask local IPs using mDNS (.local addresses), but this isn't universal.

Absolutely. VPN WebRTC protection can fail due to browser updates, extension conflicts, or configuration issues. It's good practice to test periodically, especially after browser updates or when using a new device. Trust, but verify.

Yes, that's the most private result. It means either WebRTC is disabled in your browser, or your browser is using mDNS to mask all IP addresses. Websites cannot use WebRTC to discover any of your IP addresses.

Generally, no. Incognito mode doesn't disable WebRTC by default in most browsers. However, some browsers (like Brave) have stricter privacy settings in private windows. Always test in the mode you actually use for sensitive browsing.

Complete Your Privacy Check

WebRTC is just one potential leak. For comprehensive privacy protection, also check: