Check if WebRTC is leaking your real IP address. Discover all IPs your browser exposes through STUN server queries — even those hidden behind a VPN or proxy.
Connects to public STUN servers to discover every IP address your browser exposes through the WebRTC protocol.
Identifies private IPs (192.168.x.x, 10.x.x.x) that WebRTC may reveal even behind a VPN or proxy.
Compares WebRTC-discovered public IPs against your connection IP to detect real address leaks.
Confirms whether your VPN or proxy properly blocks WebRTC requests. Essential for privacy-sensitive browsing.
Examines all ICE candidates — host, srflx, and relay — for a complete picture of exposed network interfaces.
Runs entirely in your browser using native WebRTC APIs. No extensions or downloads needed.
Click Start Leak Test. The tool creates a temporary WebRTC connection and queries public STUN servers to discover all IP candidates.
See every IP found through WebRTC — local (private) and public (internet-facing) — each with its type and origin.
The tool compares discovered IPs against your expected public IP. If a mismatch is found, WebRTC is leaking your real IP.
WebRTC (Web Real-Time Communication) is a browser technology that enables video calls, file sharing, and peer-to-peer connections. To work, it needs to discover your network interfaces — and this is where the privacy risk lies.
When you connect through a VPN or proxy, your traffic is routed through an intermediary server. However, WebRTC operates at the browser level and can bypass your proxy entirely, sending STUN requests that reveal your real public IP to any website that asks for it.
For proxy users, this means a website could see both your proxy IP (from regular HTTP traffic) and your real IP (from WebRTC), completely defeating the purpose of using a proxy in the first place.
This is why testing for WebRTC leaks is essential before any privacy-sensitive browsing, web scraping, or data collection. Combined with SpyderProxy's residential proxies, disabling or controlling WebRTC ensures complete IP anonymity.
A WebRTC leak occurs when the WebRTC protocol reveals your real public or local IP address, bypassing your VPN or proxy. WebRTC uses STUN/TURN servers to establish peer-to-peer connections, and this process can expose IPs your VPN is supposed to hide.
WebRTC discovers your network interfaces to establish connections. It sends requests to STUN servers which return your public IP. This happens at the browser level, often bypassing VPN routing, meaning any website running WebRTC JavaScript can discover your real IP.
Some VPNs block WebRTC at the network level, but many do not. You may need to disable WebRTC in browser settings, use an extension, or use Tor which disables WebRTC by default.
In Firefox: go to about:config and set media.peerconnection.enabled to false. In Chrome: use an extension like WebRTC Leak Prevent. Alternatively, use browser profiles that block WebRTC at the network level.
ICE candidates are potential network addresses for peer connections. There are three types: host (local IPs), srflx (public IP via STUN), and relay (TURN server). Each can leak different information about your network.
No. The test runs entirely in your browser. No IPs or results are sent to our servers. STUN queries go directly from your browser to public STUN servers.
Your device may have multiple interfaces (Wi-Fi, Ethernet, VPN tunnel, IPv4/IPv6). WebRTC discovers all of them. Seeing multiple IPs is normal; the concern is whether any reveal your real identity.
Route all traffic through SpyderProxy's residential and datacenter proxies for complete IP protection.
Get Residential Proxies