🔍 WebRTC Leak Test – Is Your Real IP Address Exposed?

WebRTC (Web Real-Time Communication) is a browser technology used for video calls, voice chat, and peer-to-peer file transfers. To establish direct connections between peers, it uses a protocol called STUN (Session Traversal Utilities for NAT) which requires discovering your real IP address — both local (LAN) and public.

A WebRTC leak happens when your browser exposes these IP addresses to websites you visit, even when you're connected to a VPN. The website never requested your IP directly — the browser just handed it over as part of the WebRTC handshake process. This is one of the most common ways VPN users get de-anonymized without knowing it.

No. This test runs entirely in your browser using JavaScript. We create a local WebRTC connection that queries public STUN servers (operated by Google and others) to discover your IP addresses. The results are displayed directly in your browser — nothing is transmitted to myip.casa servers. You can verify this by opening your browser's developer tools and monitoring network requests while the test runs.

Seeing a local (private) IP like 192.168.x.x or 10.x.x.x is very common and not a critical privacy issue on its own — these addresses are internal to your network and cannot be used to identify you on the internet. However, they can be used for browser fingerprinting to track you across sessions, and they can reveal that you're on a corporate or home network.

The more serious concern is when WebRTC exposes your real public IP — the one assigned by your ISP — while you think you're hidden behind a VPN. That is a genuine privacy leak.

Chrome and Chromium-based browsers (Edge, Opera, Vivaldi) are the most vulnerable because they do not offer a native setting to disable WebRTC. You must use a browser extension to prevent leaks.

Firefox allows you to disable WebRTC entirely via about:config → media.peerconnection.enabled = false, making it easier to protect yourself natively.

Brave has built-in WebRTC protection under Privacy settings, blocking non-proxied UDP and preventing IP exposure.

Safari implements WebRTC but with stricter privacy controls — leaks are rare but not impossible.

Not all VPNs handle WebRTC leak prevention at the browser level. Some VPNs route your traffic correctly but don't intercept WebRTC STUN requests, which bypass the VPN tunnel and reach the internet directly. This is especially common with browser-based VPN extensions versus full system-level VPN clients.

If your VPN claims WebRTC protection but you're still seeing a leak here, check: (1) whether the protection requires a separate browser extension, (2) whether the setting is actually enabled in your VPN app, and (3) whether you might have multiple network interfaces active that bypass the VPN.

Yes. Disabling WebRTC entirely prevents any site from using real-time communication features (video calls in the browser, etc.) but completely eliminates the risk of IP leaks.

• Firefox: Navigate to about:config, find media.peerconnection.enabled, and set it to false.
• Chrome/Edge: Install the extension "WebRTC Control" or "WebRTC Leak Prevent" from the respective extension store.
• Brave: Go to Settings → Privacy and Security → WebRTC IP Handling Policy → select "Disable Non-Proxied UDP".

Note that disabling WebRTC will break browser-based video conferencing tools like Google Meet, Jitsi, and similar services.