WebRTC Leak Auditor

Verify if your browser is leaking your true identity behind a VPN.

Protocol: STUN_AUTH_READY
Global Routing Endpoint (Public IP)
Awaiting Scan...
This is the IP websites use to identify your location.
Internal Subnet Endpoint (Local IP)
--.---.--.--
This identifies your device inside your local network.

The Invisible Leak: Why Your VPN Might Be a False Security Blanket

In the digital theater of privacy, we often rely on Virtual Private Networks (VPNs) to mask our geographic locations and internet identities. However, a fundamental browser technology known as WebRTC (Web Real-Time Communication) often acts as a back-door entrance for websites to see your true IP address. Even with a high-end VPN active, a simple script can bypass your encrypted tunnel and query your operating system for its native ISP-assigned address. The WebRTC Leak Auditor on this Canvas is a clinical diagnostic utility designed to reveal this hidden vulnerability before you compromise your anonymity.

The Human Logic of Identity Disclosure

To understand why a WebRTC leak is dangerous, we must break down the protocol into plain English logic. We define your Anonymity Quotient through these core logical pillars:

1. The Peer-to-Peer Paradox

"WebRTC allows two browsers to talk directly to each other without a middleman. To do this, your browser must shout its address to the network. If your browser shouts its true address instead of your VPN address, your privacy is compromised."

2. The STUN Request logic (LaTeX)

WebRTC uses STUN (Session Traversal Utilities for NAT) servers to discover your IP. The logic follows a simple handshake:

$$\text{Browser} \xrightarrow{\text{UDP Request}} \text{STUN Server} \xrightarrow{\text{External IP Address}} \text{Browser}$$
If the STUN server returns your original ISP IP while your VPN is active, you are witnessing a WebRTC Leak.

Chapter 1: The Anatomy of a Privacy Failure

WebRTC was designed for efficiency, not anonymity. It is an open-source project that provides web browsers and mobile applications with real-time communication (RTC) capabilities via simple APIs. It is the engine behind Discord, Zoom-in-browser, and Google Meet. However, to establish these connections with the lowest possible latency, WebRTC needs to know your Network Endpoints.

1. STUN, TURN, and ICE: The Discovery Engine

When you start a WebRTC-enabled session, your browser uses the ICE (Interactive Connectivity Establishment) protocol. ICE uses STUN and TURN servers to find out how other people can reach you. The problem is that many browsers do not force these requests through the VPN's Network Interface. Instead, they query the Operating System's physical hardware interface directly. This bypasses the encryption layer and leaks your metadata.

2. Local IP Disclosure and Hardware Fingerprinting

Beyond your public IP, WebRTC often discloses your Internal Network IP (e.g., 192.168.1.5). While this doesn't reveal your physical location, it provides a unique "Internal Signature" that websites can use for Browser Fingerprinting. By tracking your local IP, a site can tell if you are returning under a new public IP, effectively rendering your 'clear cookies' efforts useless.

THE "SOVEREIGN" SECURITY RULE

True digital privacy is not a product you buy; it is a configuration you maintain. Use this Canvas tool to verify your 'Leak Score' every time you update your browser or change your VPN provider. Technology evolves faster than privacy policies.

Chapter 2: Deciphering the Results of Your Audit

When you execute a scan on our tool, you are looking for specific indicators of a compromised session. We categorize these signals using a Threat Probability Metric:

  • Green (Secure): Both the Public IP and Local IP detected match your VPN exit node or are completely obscured. This means your browser is properly sandboxing its STUN requests.
  • Yellow (Information Leak): Your public IP is masked, but your internal Local IP is visible. This is a moderate risk for cross-site tracking and network mapping.
  • Red (Critical Failure): Your true ISP-assigned Public IP is visible even while your VPN is active. This is a total privacy failure. Stop browsing immediately and harden your settings.

Chapter 3: Strategic Hardening - How to Seal the Leak

If this tool detects a leak, don't panic. You have three primary methods to reclaim your digital sovereignty:

A. Browser Extension Layer

Extensions like uBlock Origin have built-in settings to disable WebRTC IP disclosure. In uBlock, go to 'Dashboard' > 'Privacy' and check the box that says 'Prevent WebRTC from leaking local IP addresses'.

B. Firefox Native Disabling

Firefox is currently the only major browser that allows you to turn off WebRTC entirely without an extension. Type about:config into your address bar, search for media.peerconnection.enabled, and set it to false. Note that this will break browser-based video calls.

C. Network-Level Firewalling

Advanced users can block STUN requests at the router level by blacklisting standard STUN ports (UDP 3478). This ensures that no device on your network can inadvertently disclose its identity to a remote server.

Browser Type Leak Vulnerability Strategic Fix
Chrome / Edge High Use 'WebRTC Leak Prevent' extension.
Firefox Moderate Change about:config settings manually.
Brave Low Enabled by default in Shields (Fingerprinting protection).
Safari High Enable 'Hide IP Address' in Privacy Settings.

Chapter 4: The Impact of IPv6 on Modern Leaks

As the internet transitions from IPv4 to IPv6, the complexity of leaks increases. IPv6 addresses are often tied directly to the MAC address (hardware ID) of your device. If your VPN only tunnelizes IPv4 traffic, WebRTC will simply use the IPv6 stack to broadcast your true identity. This is why our tool performs a Dual-Stack Audit to ensure neither protocol is betraying your location.


User Tips & Engaging Privacy Tricks

The Airplane Reset

If you detect a leak, simply toggling your VPN off and on isn't enough. Your browser might have cached your real IP. After fixing your settings, restart your browser and perform a fresh scan on this Canvas to verify the fix.

The "Fingerprint" Test

Use your Local IP as a test. If you visit a site, clear your cookies, and the site still remembers you—it's likely using WebRTC device mapping. This tool helps you identify if that data is even reachable by the site.

Frequently Asked Questions (FAQ) - Privacy Intelligence

Why does my "Local IP" look like a long string of letters?
This is likely an mDNS (multicast DNS) address. To improve privacy, modern browsers often obfuscate your local IP (like 192.168.1.1) with a unique, temporary UUID (e.g., f7c1...local). If you see this, it means your browser is successfully protecting your internal network topography. You are secure!
Is my text or IP data sent to your servers?
100% Private. All WebRTC IP discovery and terminal readouts happen entirely within your browser's local RAM. We have zero backend infrastructure capable of seeing, logging, or storing your IP address. This tool is a purely Client-Side diagnostic.
Can I use this on my Android phone?
Perfectly. Mobile Chrome and mobile Firefox are just as susceptible to WebRTC leaks as their desktop counterparts. Open this page on your Android device, tap the three dots, and select "Add to Home Screen" to use this as an offline privacy-check utility whenever you connect to a public Wi-Fi.

Audit Your Shadow

Stop guessing about your browser security. Quantify your exposure, identify the leaks, and ensure your identity remains yours alone. Knowledge is the ultimate encryption.

Initialize Privacy Audit

Recommended Logic Tools

Curating similar automated utilities...