Test Your Browser for WebRTC Leaks

Find out if your browser is leaking your true identity. See if WebRTC is bypassing your VPN right now.

Your WebRTC Leak Test Result

Checking...

Understanding Your Test Result

Below you can see all possible statuses the WebRTC Leak test may display, ordered from best to worst protection.

Possible statuses (from best to worst protection)

No leak (WebRTC disabled)	WebRTC is disabled in your browser, so nothing can leak through it.
No leak (VPN protected)	Your VPN is on and WebRTC doesn't reveal any public IP address.
No leak (protected)	WebRTC doesn't reveal any public IP address.
No leak (VPN working)	WebRTC only shows your VPN's IP address. Your real IP stays hidden.
No leak	WebRTC shows the same IP as your public IP — no additional IPs are exposed.
No VPN detected	WebRTC shows your public IP address. This is normal without a VPN.
Leak detected	WebRTC is exposing your real IP address. Websites can see your location despite your VPN.

What is a WebRTC Leak?

WebRTC (Web Real-Time Communication) is a browser technology that enables video calls, voice chat, and peer-to-peer file sharing directly in the browser — without plugins. Sites like Google Meet, Discord, and Zoom use it.

To establish a direct connection between two users, WebRTC needs to know both parties' IP addresses. It does this using a protocol called ICE (Interactive Connectivity Establishment), which can discover your real IP address even if you are using a VPN.

A WebRTC leak is one of the most common ways a website can see your real IP address despite an active VPN. It bypasses the VPN entirely at the browser level — not a network level failure, but a browser-level one.

How Does This Test Work?

This test runs entirely in your browser — no data is sent to my server:

Your public IP address is fetched via ipify.org — this is the IP your VPN (or ISP) presents to the outside world
An RTCPeerConnection is created using multiple STUN servers (Google, Cloudflare, Nextcloud) — this is the same mechanism websites use for WebRTC calls
Any IPs discovered via WebRTC are compared against your public IP — a mismatch means a leak
Private/local IPs (192.168.x.x, 10.x.x.x) are excluded — only public IPs that reveal your identity are reported

Who Is Affected?

WebRTC leaks affect Chromium-based browsers (Chrome, Edge, Brave, Opera) and Firefox by default. Safari has WebRTC restrictions that generally prevent leaks.

Browser	Default Risk	Fix
Tor Browser	None	WebRTC disabled by default — no action needed
Brave (Tor Mode)	None	WebRTC blocked in Tor mode — no action needed
Mullvad Browser	None	WebRTC disabled by default — no action needed
LibreWolf	None	WebRTC disabled by default — no action needed
Brave	Low	Blocked by default — verify in Settings → Privacy and Security → WebRTC IP handling policy
Safari	Low	Generally not vulnerable — WebRTC does not expose local IPs
Firefox	High	Set `media.peerconnection.enabled` to `false` in `about:config`
Google Chrome	High	VPN with WebRTC protection, or install WebRTC Leak Prevent extension
Microsoft Edge	High	VPN with WebRTC protection, or install WebRTC Leak Prevent extension
Opera	High	VPN with WebRTC protection — Opera's built-in VPN does not block WebRTC leaks
Samsung Internet	High	VPN with WebRTC protection — no browser-level fix available

How to Fix a WebRTC Leak?

Use a VPN with a browser extension: Most leading VPN providers — including NordVPN, Surfshark, ExpressVPN, and ProtonVPN — offer browser extensions that block WebRTC leaks automatically. For maximum protection, pair your VPN with its browser extension, or choose a privacy-first browser like Mullvad Browser or Tor Browser, where WebRTC is disabled by default.
Firefox: Go to about:config, search for media.peerconnection.enabled, and set it to false in advanced configuration — this disables WebRTC entirely
Chrome / Edge: Install a browser extension such as WebRTC Leak Prevent or uBlock Origin (with WebRTC blocking enabled in advanced settings)
Switch to Brave: Brave blocks WebRTC IP leaks by default under Settings → Privacy and Security → WebRTC IP handling policy
Disable WebRTC at the OS level: Some VPN clients (Mullvad) can block WebRTC system-wide regardless of browser

Note: Disabling WebRTC will break browser-based video calls (Google Meet, Zoom web, Discord). If you need both privacy and video calls, use a VPN that handles WebRTC at the client level rather than disabling WebRTC in the browser.

Fixed the WebRTC leak? Run the VPN Test to confirm that DNS and IPv6 traffic are protected too.

WebRTC and Tor

The Tor Browser disables WebRTC by default — it is one of the most effective browsers for preventing this type of leak. However, Tor routes all traffic through the Tor network, which significantly reduces browsing speed. It is not a practical solution for everyday use if you need fast, real-time communication.

The Verdict: Close the WebRTC Loophole

WebRTC leaks are silent and dangerous — websites can call a JavaScript API that bypasses your VPN entirely and reveals your home IP address without any visible indication.

The most reliable fix is a VPN that actively blocks WebRTC at the client level. The VPNs below include WebRTC leak protection and have been tested to confirm it works.

View VPNs with WebRTC Leak Protection →

Frequently Asked Questions

What is a WebRTC leak?

A WebRTC leak occurs when your browser's WebRTC implementation exposes your real IP address to websites — bypassing your VPN or proxy. WebRTC is a browser API used for real-time communication (video calls, file sharing). To establish peer-to-peer connections, it uses a protocol called STUN that can reveal your local and public IP addresses, even if your internet traffic is routed through a VPN.

Why does WebRTC bypass a VPN to reveal my real IP?

Think of your VPN as a secure tunnel for your mail. WebRTC is like a courier who ignores the tunnel and takes a shortcut over the hill to deliver your package faster. While it's great for speed (video calls), the courier reveals your home address to everyone watching the shortcut. This test catches that "courier" in the act.

Which browsers are affected by WebRTC leaks?

Chrome, Firefox, Opera, and most Chromium-based browsers (Edge, Brave, Vivaldi) all implement WebRTC and can potentially leak your IP. Mobile browsers are also affected — Chrome for Android can leak your real IP just like its desktop version. Safari on iPhone has stricter defaults and is less likely to leak, but is not immune. If you use a VPN on your phone, run this test on mobile too. Brave has built-in WebRTC leak protection. Firefox allows you to disable WebRTC entirely via about:config (set media.peerconnection.enabled to false).

How do I stop a WebRTC leak?

The most reliable options: use Brave (has built-in WebRTC protection under Privacy settings), use a VPN with WebRTC leak protection (NordVPN, Mullvad), or install a browser extension like uBlock Origin (enable "Prevent WebRTC from leaking local IP addresses" in its settings). In Firefox, set media.peerconnection.enabled = false in about:config. Keep in mind: disabling WebRTC will break browser-based video tools like Google Meet, Discord, and Zoom. If you rely on these for work, use a VPN with dedicated WebRTC protection instead of disabling the API entirely.

Does a VPN automatically fix WebRTC leaks?

Not always. Many VPNs protect your HTTP/HTTPS traffic but don't intercept WebRTC traffic, leaving your real IP visible via STUN. VPNs that explicitly advertise WebRTC leak protection include NordVPN, Mullvad, and ExpressVPN — they route or block WebRTC requests to prevent exposure. The safest way to verify is to run this test with your VPN connected. If the test shows your real IP alongside the VPN IP, your VPN is not blocking WebRTC leaks.

Does WebRTC affect online gaming?

Yes. Many browser-based games and cloud gaming platforms like GeForce Now and Xbox Cloud Gaming use WebRTC for low-latency connections. If you're a gamer, I recommend using a VPN that supports UDP-based filtering to stay private without adding significant lag to your session.