WebRTC Leak Test
Run a WebRTC leak test to check whether your browser exposes local IPs, public IP mismatches, or mDNS-obfuscated host candidates that could bypass a VPN.
When you run the WebRTC leak test, your browser may contact the listed Google and Cloudflare STUN servers to gather ICE candidates.
What This Tool Does
Our free WebRTC leak test checks whether your browser's WebRTC stack reveals your real IP address. WebRTC enables video calls and peer-to-peer communication, but it can bypass VPNs and expose local and public IPs. Run the test to check for WebRTC leaks and verify your privacy setup.
Common Use Cases
- Run a WebRTC leak test after connecting to a VPN
- Check whether WebRTC exposes your real public IP
- Verify VPN protection isn't bypassed by WebRTC
- Check browser privacy settings and leak-blocking extensions
- Audit your privacy setup before sensitive browsing
- Debug video call connectivity issues
Frequently Asked Questions
What is a WebRTC leak test?
A WebRTC leak test checks whether your browser exposes local or public IP addresses through WebRTC APIs. Run the test on this page: it gathers ICE candidates (using listed STUN servers) and reports any IPs that appear, so you can see if a VPN is bypassed.
What is a WebRTC leak?
WebRTC can expose your real public and local IP addresses directly through browser APIs, bypassing VPN tunnels. This happens because WebRTC was designed for peer-to-peer communication and needs to discover your real network addresses to establish connections.
How do I prevent WebRTC leaks?
Disable WebRTC in browser settings (Firefox: about:config → media.peerconnection.enabled = false), use browser extensions like uBlock Origin or WebRTC Leak Prevent, or use browsers like Brave that block WebRTC leaks by default.
Will disabling WebRTC break websites?
Disabling WebRTC may affect video conferencing (Zoom, Google Meet, Discord), voice calls in browsers, and some file sharing features. You can use selective blocking to allow WebRTC only on trusted sites.