WebRTC Leak Test
Check if your web browser or VPN is exposing your real public IP or internal private network address through WebRTC STUN requests. Runs 100% locally in your browser.
| Type | Protocol | IP / Hostname Address | Port | Classification |
|---|---|---|---|---|
| Waiting for ICE gathering to complete... | ||||
Understanding WebRTC Leaks & How They Expose Your IP
WebRTC (Web Real-Time Communication) enables voice, video calling, and P2P data sharing directly between browsers without plugins. To establish direct peer connections between users behind NAT routers and firewalls, WebRTC uses STUN (Session Traversal Utilities for NAT) servers to discover the device's external public IP and local network interfaces.
The VPN Leak Vulnerability
Even when connected to a VPN or proxy, some browsers allow WebRTC STUN requests to bypass the encrypted VPN tunnel, sending requests directly over your default ISP gateway and revealing your actual location.
Local IP & mDNS Masking
Modern browsers often generate randomized .local mDNS addresses to avoid exposing internal LAN IPs (e.g. 192.168.1.15), protecting you against local network fingerprinting.
No Plugins Required
Because WebRTC is built natively into HTML5, any website can execute JavaScript to read your STUN candidates without asking for permission.
How to Prevent WebRTC Leaks in Your Browser
Install the uBlock Origin extension and enable "Prevent WebRTC from leaking local IP addresses" in settings, or install the official WebRTC Network Limiter extension from Google.
Type about:config into Firefox address bar, search for media.peerconnection.enabled, and toggle it to false to completely disable WebRTC.
Navigate to brave://settings/shields and set the WebRTC IP Handling Policy to "Disable Non-Proxied UDP".