WebRTC is only half the picture — check your DNS for leaks too.
What is a WebRTC Leak?
WebRTC (Web Real-Time Communication) is a browser technology that enables peer-to-peer audio, video, and data sharing directly between browsers — it powers video calls, file sharing, and real-time messaging without plugins. To establish these connections, WebRTC needs to discover your device's IP addresses, including both your local network address and your public IP.
The problem is that this IP discovery process happens at the browser level, completely bypassing your VPN tunnel. Even if your VPN is active and your regular traffic is encrypted and routed through the VPN server, JavaScript running on any website can use WebRTC to query your real IP address directly. The website then sees both your VPN's IP and your actual IP, defeating the entire purpose of using a VPN for privacy.
This affects Chrome, Firefox, Edge, and Opera by default. Safari has partial WebRTC support. Brave disables WebRTC fingerprinting by default. The only reliable fixes are disabling WebRTC in your browser settings, using a browser extension, or using a VPN that specifically blocks WebRTC leaks at the network level — like our fix guide explains.
How to Fix a WebRTC Leak
Chrome
Chrome doesn't have a built-in toggle to disable WebRTC. Install the "WebRTC Leak Prevent" extension or "uBlock Origin" with WebRTC blocking enabled. For enterprise users, set a Chrome policy to disable non-proxied UDP. Full Chrome guide →
Firefox
Type about:config in the address bar, search for media.peerconnection.enabled, and set it to false. This completely disables WebRTC. Full Firefox guide →
Safari
Safari limits WebRTC exposure by default and only allows it for sites you grant camera/mic permission. For full protection, go to Safari → Settings → Advanced → check "Show Develop menu", then Develop → Experimental Features → uncheck WebRTC.
Edge
Edge is Chromium-based, so the same Chrome extensions work. Install "WebRTC Leak Prevent" from the Edge Add-ons store. Alternatively, navigate to edge://flags and search for WebRTC-related flags.
Easiest Fix: Use a VPN With Built-In Protection
The simplest solution is a VPN that blocks WebRTC leaks automatically at the network level, so you don't need extensions or manual configuration in every browser.
Chrome, Firefox, Edge, and Opera all expose IP addresses via WebRTC by default. Brave blocks WebRTC fingerprinting by default. Safari has limited WebRTC support and only exposes IPs to sites with explicit camera/mic permission. Tor Browser disables WebRTC entirely.
Not sure if your DNS is leaking? Find out in seconds.