WebRTC Leak Check
Inspect browser WebRTC leaks, compare HTTP proxy/VPN egress with STUN candidates, and verify network anonymity.
Testing WebRTC and Network Egress...
Gathering ICE Candidates...No WebRTC Leak Detected
Your WebRTC STUN egress matches your HTTP public IP or WebRTC is properly routed. Your true IP address is not leaking.
CRITICAL: WebRTC Leak Detected!
Your real IP address is leaking via WebRTC! WebRTC bypassed your Proxy/VPN connection and revealed your true ISP egress.
tools/webrtc-leak-check.tips.0Local Private IP Exposed
Your internal LAN IP address is exposed to websites through WebRTC host candidates instead of being masked with mDNS.
WebRTC Disabled or Blocked
WebRTC peer connection is disabled or blocked by your browser/ad-blocker. You are completely immune to WebRTC leaks.
HTTP Public IP (Browser Egress)
HTTP EgressThis is the IP address seen by websites through standard HTTP requests (your active Proxy, VPN, or ISP IP).
-
| Country: | - |
| City: | - |
| ISP / Provider: | - |
| ASN: | - |
| Timezone: | - |
| Security: | Checking... |
WebRTC Public IP (STUN Candidate)
Evaluating...This is the public IP discovered by WebRTC STUN requests. If it differs from your HTTP IP, WebRTC is leaking!
-
| Country: | - |
| City: | - |
| ISP / Provider: | - |
| ASN: | - |
| Candidate: | srflx (STUN) |
| Verdict: | - |
WebRTC Local / Host IP
Checking...Internal LAN IP address or privacy-preserving mDNS candidate generated by your browser.
-
IPv6 WebRTC Status
Checking...Checks if your device leaks a native IPv6 address via WebRTC while browsing on an IPv4-only proxy.
-
Proxy Server WebRTC Risk Analyzer
Test an external proxy server and evaluate its WebRTC leak vulnerabilities before using it in your browser.
WebRTC Vulnerability Assessment
Comprehensive real-time log of all Interactive Connectivity Establishment (ICE) candidate tokens gathered.
| # | Type | Protocol | IP Address / Host | Port | Priority | Raw Candidate |
|---|---|---|---|---|---|---|
| Gathering ICE Candidates... | ||||||
Media Device Fingerprinting Check
Checks if WebRTC MediaDevices API exposes hardware device IDs (microphones, cameras, headphones) to track you.
| Device Type | Device Label / Model | Device ID Hash |
|---|---|---|
| Scanning connected media devices... | ||
How to Fix WebRTC Leaks in Your Browser
Google Chrome / Chromium
Install a trusted WebRTC blocking extension such as WebRTC Control or uBlock Origin (check "Prevent WebRTC from leaking local IP addresses" under Privacy settings).
Mozilla Firefox
Open about:config in Firefox. To disable WebRTC completely, set media.peerconnection.enabled to false. When using a proxy, set media.peerconnection.ice.proxy_only to true.
Brave Browser
Go to Settings > Privacy and Security > Shields. Under WebRTC IP Handling Policy, select "Disable Non-Proxied UDP".
Microsoft Edge
Type edge://flags in the URL bar, search for "Anonymize local IPs exposed by WebRTC" and enable it. For complete protection, use a WebRTC control extension.
Apple Safari
Safari enables mDNS candidate masking by default on macOS and iOS. To further restrict WebRTC, open Safari Settings > Advanced > Develop menu, and configure WebRTC ICE candidate restrictions.
About WebRTC Leak Check & Proxy Anonymity
WebRTC (Web Real-Time Communication) is an open-source protocol built into modern browsers that enables peer-to-peer voice, video, and data transmission without external plugins.
To establish direct peer connections, WebRTC uses STUN (Session Traversal Utilities for NAT) servers to discover your device's public and local IP addresses. However, WebRTC queries are sent over UDP and often bypass configured HTTP/HTTPS or SOCKS proxies, silently exposing your real public IP and location to any website you visit.
This WebRTC Leak Check tool inspects all ICE candidates gathered by your browser, compares your observed HTTP egress IP (Proxy/VPN) with the WebRTC-exposed IP, evaluates local network exposures, tests proxy server WebRTC vulnerability, and verifies device fingerprinting risks.
Key features
- Real-Time STUN Leak Detection Initiates local WebRTC peer connection handshakes with reliable STUN servers to detect public IPv4 and IPv6 addresses exposed by Interactive Connectivity Establishment (ICE).
- HTTP vs WebRTC Side-by-Side Comparison Compares your apparent HTTP browser IP (Proxy/VPN address) directly against the WebRTC STUN candidate IP to pinpoint stealth leaks instantly.
- Local Network & mDNS Exposure Analysis Identifies whether private LAN IP ranges (192.168.x.x, 10.x.x.x) are exposed or properly masked by modern browser mDNS obfuscation.
- Proxy Server WebRTC Risk Checker Test arbitrary proxy servers (HTTP, HTTPS, SOCKS4, SOCKS5) for latency and anonymity, accompanied by an architectural WebRTC leak risk assessment.
- Media Device Fingerprinting Inspection Audits connected microphones, cameras, and audio output devices to ensure hardware identifiers are not leaking for cross-site browser fingerprinting.
- Comprehensive ICE Candidate Logger Inspect full raw ICE candidate strings with detailed breakdown of candidate type (srflx, host, relay), protocol (UDP/TCP), port, and priority.
How to test and fix WebRTC leaks
Follow these steps to diagnose your network anonymity and prevent IP exposure when using proxies or VPNs.
- Run the initial WebRTC baseline check Open the page to automatically discover your current HTTP public IP address and the IP addresses exposed via WebRTC STUN requests.
- Connect to your Proxy Server or VPN Activate your VPN client, configure your browser proxy extension, or set up your system SOCKS5 proxy, then click the Retest button.
- Evaluate the side-by-side leak verdict Check if the WebRTC Public IP matches your Proxy/VPN IP. If the WebRTC candidate shows your original ISP IP while HTTP shows the proxy, your connection is actively leaking.
- Test proxy servers and apply browser mitigations Use the Proxy Risk Analyzer tab to evaluate your proxy protocol, and follow the remediation guide to disable WebRTC or enable strict proxy-only routing.
Usage tips
- Standard HTTP/HTTPS proxies only handle TCP web requests and cannot route WebRTC UDP traffic, almost always leading to leaks unless WebRTC is disabled.
- In Mozilla Firefox, set media.peerconnection.ice.proxy_only to true in about:config to force WebRTC traffic through configured proxies.
- In Chromium-based browsers (Chrome, Edge, Brave, Opera), use extensions like uBlock Origin or WebRTC Control to prevent STUN requests on non-proxied interfaces.
- Always verify IPv6 WebRTC candidates, as many VPN providers and proxies only tunnel IPv4, leaving native IPv6 addresses completely exposed.