WebRTC Leak Test
Is WebRTC exposing your real IP address around your proxy or VPN? This test runs entirely in your browser — the same trick any website can use against you.
Probing WebRTC… collecting ICE candidates and comparing them with your HTTP exit IP.
How to fix a WebRTC leak
- Firefox: open about:config, set media.peerconnection.enabled to false.
- Chrome / Edge / Brave: install a WebRTC-control extension (e.g. “WebRTC Leak Prevent”) or set the IP-handling policy to “disable non-proxied UDP” where your browser exposes it.
- Proxy users: prefer SOCKS5 with remote DNS and make sure your tool or browser profile routes UDP/WebRTC through the proxy — an HTTP proxy alone does not cover WebRTC’s peer connections.
- Antidetect browsers: use a profile with WebRTC set to “disabled” or “altered” so the reported address matches your proxy exit IP.
WebRTC is a browser technology built for voice calls, video chat and peer-to-peer file sharing. To set up those direct connections, your browser uses a protocol called ICE, which discovers every network address it can reach you on — including your real public IP address. The catch: any website can run the same discovery with a few lines of JavaScript, silently, the moment the page loads. Neither your address bar nor a padlock icon will warn you.
That is what makes a WebRTC leak so dangerous for proxy and VPN users. Your HTTP traffic may be routed cleanly through an exit node in another country, while WebRTC happily hands your home IP to every site you visit. Platforms that fight multi-accounting and automation use exactly this signal: if the IP in your browser's WebRTC candidates doesn't match the IP your requests arrive from, the connection is flagged as proxied and the account or session is burned. Our test above reproduces the check — it gathers your browser's ICE candidates and compares the public addresses against the IP websites see over plain HTTP.
Reading the result is simple. If the public (srflx) addresses match your HTTP exit IP, or WebRTC returns no public address at all, you are covered. If WebRTC exposes a different public IP, that address is almost certainly your real one leaking around the tunnel. Modern browsers also mask local addresses behind random .local mDNS names — those masked entries are expected and harmless; the public candidates are the ones that matter.
Fixing a leak takes minutes. Firefox users can disable WebRTC entirely in about:config; Chrome users can install a WebRTC-control extension or tighten the browser's IP-handling policy. If you run proxies, prefer SOCKS5 with remote DNS and a browser profile that forces WebRTC through the proxy — or disables it outright. Antidetect browsers offer this as a per-profile setting. Whichever route you take, re-run this test afterwards: it is the only way to be sure the leak is actually closed.
Frequently asked questions
What is a WebRTC leak?
A WebRTC leak happens when your browser's WebRTC/ICE discovery reveals your real public IP address to websites even though your normal traffic goes through a proxy or VPN. Any site can trigger it with JavaScript — no permission prompt, no visible sign.
How does this WebRTC leak test work?
The test opens an RTCPeerConnection in your browser, collects the ICE candidates it produces (host, srflx, relay), and compares the public srflx addresses with the IP address websites see over plain HTTP. A mismatch means WebRTC is exposing an address outside your tunnel. Everything runs locally in your tab — no data is sent to our servers except the standard IP lookup used for comparison.
Does using a VPN prevent WebRTC leaks?
Not always. A well-configured VPN that routes all UDP traffic prevents them, but some VPN apps, browser-based proxies and split-tunnel setups leave WebRTC outside the tunnel. HTTP proxies never cover WebRTC at all. The only reliable check is to test — which is what this page does.
How do I disable WebRTC?
In Firefox, set media.peerconnection.enabled to false in about:config. In Chrome and Edge, use a WebRTC-control extension or set the IP handling policy to disable non-proxied UDP. In antidetect browsers, set WebRTC to disabled or altered per profile, then re-run this test to confirm.
What does the .local address in my results mean?
Addresses ending in .local are mDNS names that modern browsers substitute for your real LAN address — a privacy feature. They identify your device on your local network only in masked form and cannot be used to locate you. Only public (srflx) candidates can leak your real address.
Proxies that don't leak around your setup
IPStation residential proxies with SOCKS5 and remote DNS keep your exit IP consistent everywhere — including WebRTC. Try 200 MB free.
View pricing