Run this WebRTC leak test to check if your browser is exposing your real public or local IP address through WebRTC APIs. If a leak is detected, we show you exactly how to fix it.
FreeGuard Internal Test Results
FreeGuard VPN blocks WebRTC IP discovery at the network level, preventing both public and local IP leaks across all tested browsers.
How WebRTC Leaks Bypass Your VPN and Expose Your Real IP Address
WebRTC uses STUN server requests to discover your IP addresses for peer-to-peer communication, and these requests can bypass your VPN tunnel entirely.
WebRTC (Web Real-Time Communication) is a browser technology that enables peer-to-peer audio, video, and data sharing without plugins. It powers video calls on platforms like Google Meet, Discord, and Facebook Messenger.
To establish peer-to-peer connections, WebRTC needs to discover your IP addresses. It does this by sending requests to STUN (Session Traversal Utilities for NAT) servers. The problem is that these STUN requests can occur outside your VPN tunnel, revealing both your public IP address and local network IP addresses.
This means that even with a VPN active, a website can use JavaScript to trigger WebRTC and discover your real IP address. The leak happens at the browser level, not the network level, which is why many VPNs that work at the system level fail to prevent it.
All major browsers — Chrome, Firefox, Edge, and Opera — have WebRTC enabled by default. Safari has WebRTC but with more restrictive default permissions.
How to Disable WebRTC in Every Major Browser
You can disable WebRTC in Firefox through about:config, use browser extensions in Chrome and Edge, or use a VPN that blocks WebRTC leaks at the network level.
Firefox: Type about:config in the address bar, search for media.peerconnection.enabled, and set it to false. This completely disables WebRTC.
Chrome / Edge / Opera: These browsers do not allow disabling WebRTC through settings. Install a WebRTC leak prevention extension, or use a VPN with built-in WebRTC leak protection. Note that extensions can only limit WebRTC, not fully disable it.
Safari: Go to Preferences → Advanced → Show Develop menu. In the Develop menu, uncheck “Enable WebRTC MDNS ICE candidates” to prevent local IP leaks.
Best approach: Rather than disabling WebRTC (which breaks video calling), use a VPN like FreeGuard that intercepts WebRTC STUN requests at the network level, ensuring only the VPN IP is returned.
How to Protect Yourself in 3 Steps
- Step 1: Run the WebRTC leak test above with your VPN connected to see if your real IP is exposed
- Step 2: If a leak is detected, check your browser settings or install a WebRTC leak prevention extension
- Step 3: Run the test again to confirm the leak is fixed and only your VPN IP is visible
Frequently Asked Questions
What is WebRTC and why does it exist in my browser if it creates a potential privacy vulnerability to ensure my personal data and browsing activity remain fully private?
WebRTC enables real-time video calls, voice chat, and file sharing directly in your browser without plugins. It is essential for services like Google Meet and Discord. The privacy risk is a side effect of its IP discovery mechanism.
Can a website discover my real IP address through WebRTC even when I am connected to a VPN and what are the most important things I should know about this?
Yes. WebRTC STUN requests can bypass VPN tunnels and reveal your real public and local IP addresses. This is why dedicated WebRTC leak protection is important.
Does disabling WebRTC in my browser affect my ability to use video calling services like Zoom or Google Meet and what are the most important things I should know about this?
Yes, disabling WebRTC breaks browser-based video calling. A better approach is using a VPN with WebRTC leak protection, which masks your IP while keeping WebRTC functional.
What is the difference between a WebRTC leak showing my public IP address versus my local or private IP and what are the most important things I should know about this?
A public IP leak reveals your ISP and approximate location to websites. A local IP leak (like 192.168.x.x) reveals your network configuration but is less identifying on its own.
Why do some VPN browser extensions fail to prevent WebRTC leaks while desktop VPN applications succeed and what are the key considerations and potential limitations that I should be aware of before proceeding?
Browser extensions operate within the browser’s sandbox and cannot fully control WebRTC at the network level. Desktop VPN apps intercept traffic at the OS level, providing more complete protection.
Is my mobile browser on Android or iOS also vulnerable to WebRTC leaks when using a VPN app and what are the most important things I should know about this?
Yes. Mobile browsers support WebRTC and can leak your IP. However, VPN apps that configure the device’s network tunnel typically prevent WebRTC leaks on mobile more effectively than on desktop.
How can I test whether a specific website is attempting to use WebRTC to discover my real IP address and what are the most important things I should know about this?
Open your browser’s developer tools (F12), go to the Console tab, and look for RTCPeerConnection API calls. Our test above also checks for all WebRTC leak vectors automatically.
Will using browser incognito or private mode prevent WebRTC from leaking my real IP address to websites and what are the most important things I should know about this?
No. Incognito mode does not disable WebRTC. Your IP can still be leaked through STUN requests in private browsing mode. You need a VPN or WebRTC-specific protection.
WebRTC is enabled by default in Chrome, Firefox, Edge, and Opera, potentially exposing local and public IP addresses even when using a VPN. — Mozilla Developer Network (2024)
Research shows that 20-30% of browser-based VPN extensions fail to prevent WebRTC IP leaks in their default configuration. — USENIX Security (2023)
WebRTC STUN requests can reveal both IPv4 and IPv6 addresses, bypassing VPN tunnels through direct peer-to-peer connection negotiation. — W3C WebRTC Working Group (2024)