HomeToolsIP & WebRTC Leak Test

IP & WebRTC Leak Checker

Verify if your real ISP IP or local network IP is leaking past your VPN, Proxy, or Tor connection through WebRTC STUN requests.

Diagnostic Result

Gathering WebRTC STUN Candidates...

Querying Google & Cloudflare STUN servers to detect candidate leaks...

1. Public HTTP IP
Detecting...

, ()

2. WebRTC Public Candidates
Gathering...
3. Local LAN IPs (Internal)
Detecting...

How to Disable WebRTC & Prevent IP Leaks

๐ŸฆŠ Mozilla Firefox
  1. Type about:config in address bar.
  2. Search for media.peerconnection.enabled.
  3. Toggle it to false.
๐ŸŒ Google Chrome & Edge
  1. Install extension uBlock Origin or WebRTC Leak Prevent.
  2. Under settings, enable "Prevent WebRTC from leaking local IP addresses".
๐Ÿฆ Brave Browser
  1. Go to Settings > Privacy & Security.
  2. Set "WebRTC IP Handling Policy" to Disable Non-Proxied UDP.
Deep Security Analysis

What is a WebRTC Leak & Why Do VPNs Fail to Block It?

WebRTC (Web Real-Time Communication) is an open-source standard integrated into all modern browsers that enables direct, peer-to-peer audio, video, and data transmission without requiring external browser plugins. While WebRTC powers essential tools like Google Meet, Discord, and Zoom in the browser, it contains a critical architectural security flaw for privacy-conscious users.

To establish a direct connection between two peers located behind restrictive NAT firewalls and home routers, WebRTC uses the STUN (Session Traversal Utilities for NAT) protocol over UDP packets. When a website executes a few lines of JavaScript creating an RTCPeerConnection, your browser sends a query to a public STUN server. The STUN server reflects back your true, raw external public IP address assigned by your Internet Service Provider (ISP).

Because browser STUN requests frequently bypass local proxy settings and certain flawed VPN virtual network adapter interfaces, the website learns your real geographic location and identityโ€”even while your browser status shows an active VPN connection!

The Three Types of ICE Candidates Harvested by Trackers

1. Host Candidates (LAN IP)

Reveals your internal local area network address (e.g. 192.168.1.45 or 10.0.0.12). Trackers use this to identify multiple devices on the same home network.

2. Server Reflexive (Public IP - LEAK!)

The actual public IP returned by the STUN server. If this does not match your VPN exit node IP, your entire identity and physical city are deanonymized.

3. Relay Candidates (TURN)

Traffic routed through an intermediate relay server. This is the safest candidate type because your raw IP is not disclosed to the destination peer.

Comparison: WebRTC Leaks vs DNS vs IPv6 vs HTTP Leaks

Leak VectorProtocol / MechanismWhat is Exposed to Websites?Primary Defense / Fix
๐Ÿšจ WebRTC LeakSTUN / UDP port 19302Real ISP Public IPv4/IPv6 & Local LAN IPDisable WebRTC or use uBlock Origin UDP blocking
๐ŸŒ DNS LeakDNS Queries (UDP port 53)ISP DNS Server IP & Websites you visitEnforce DNS-over-HTTPS (DoH) or VPN DNS routing
๐Ÿ”Œ IPv6 LeakIPv6 Dual-Stack RoutingGlobal IPv6 address tied to device MAC prefixDisable IPv6 in OS network adapter settings
๐Ÿ›ก๏ธ HTTP Proxy LeakX-Forwarded-For headersClient IP forwarded by transparent proxiesUse Elite / Anonymous Proxy or Full WireGuard VPN

Frequently Asked Questions (FAQ)

Will disabling WebRTC break any websites?

Disabling WebRTC will only affect browser-based real-time peer-to-peer video/voice applications (like Discord web, Google Meet, or WebTorrent). Normal video streaming (YouTube, Netflix) and regular web browsing will continue functioning 100% normally.

Why is my local IP (e.g. 192.168.1.x) showing as "mDNS shielded"?

Modern browsers implement mDNS (Multicast DNS) obfuscation, which conceals your raw local private IP behind a randomized UUID hostname (e.g. c38942b0-6fd7...local) to prevent local network fingerprinting.

Does using Tor Browser protect against WebRTC leaks?

Yes. The Tor Browser completely disables WebRTC by default at the source code level to guarantee that STUN requests can never leak your true IP address outside the Tor circuit.

How often should I test for WebRTC leaks?

You should test whenever you switch to a new VPN provider, install a browser update, or connect to a new public WiFi hotspot to ensure your privacy configuration remains unbroken.

Browser Defense Manual

Complete Guide: How to Disable WebRTC in Any Browser

Depending on your browser engine (Gecko vs Chromium vs WebKit), disabling or restricting WebRTC STUN requests requires different configuration procedures. Follow our step-by-step instructions below:

๐ŸฆŠ Mozilla Firefox (100% Native Disable)

  1. Type about:config in the URL bar and press Enter.
  2. Click "Accept the Risk and Continue".
  3. Search for media.peerconnection.enabled.
  4. Double-click the entry or click the toggle button to set its value to false.
  5. Restart Firefox and re-run this leak test. WebRTC is now completely disabled.

๐ŸŒ Google Chrome / Microsoft Edge

Chromium does not provide an official native UI flag to turn off WebRTC completely. You must use an extension or policy routing:

  1. Install the trusted open-source extension "WebRTC Control" or "uBlock Origin".
  2. In uBlock Origin settings, enable "Prevent WebRTC from leaking local IP addresses".
  3. Alternatively, use a commercial VPN browser extension that routes WebRTC traffic through its own proxy.

๐Ÿฆ Brave Browser (Built-in Shield)

  1. Open Settings โ†’ Privacy and security.
  2. Scroll to "WebRTC IP handling policy".
  3. Change the dropdown to "Disable non-proxied UDP".
  4. This ensures UDP STUN queries never bypass active proxy or VPN tunnels.

๐Ÿงญ Apple Safari (macOS & iOS)

  1. Open Safari Settings โ†’ Advanced.
  2. Check "Show features for web developers".
  3. Go to the top menu Develop โ†’ Experimental Features.
  4. Enable "WebRTC mDNS ICE Candidates" to conceal raw IP structures behind randomized tokens.

Who Needs to Test for WebRTC IP Leaks?

๐Ÿ”’ VPN & Proxy Users

Verify that the monthly subscription you pay for actual privacy isn't compromised by a silent browser UDP leak.

๐Ÿช™ Crypto & DeFi Traders

Prevent decentralized exchanges and wallet frontends from logging your real geographic identity and physical ISP connection.

๐Ÿ“ฐ Journalists & Researchers

Ensure sensitive research and anonymous sourcing cannot be tracked back to your physical home or office internet hookup.

๐Ÿ’ผ Remote Workers & Freelancers

Prevent client portals and enterprise platforms from flagging geographical anomalies or location mismatches.

๐ŸŽฎ Gamers & P2P Streamers

Protect your home network from targeted DDoS attacks by preventing malicious peers from capturing your residential IP.

๐Ÿ›ก๏ธ Privacy Enthusiasts

Audit your complete digital footprint across multiple devices and browsers with zero telemetry.