How do I fix a WebRTC leak?

Disable WebRTC in your browser settings or use a VPN that blocks WebRTC leaks. Brave browser blocks WebRTC leaks by default.

Does this test actually leak my IP?

No — this is a read-only test. We detect and display your IPs but do not store or transmit them anywhere.

Privacy Tool

WebRTC Leak Test

Q: What is a WebRTC leak?

WebRTC can expose your real IP address even when using a VPN, because WebRTC makes direct peer connections that bypass the VPN tunnel.

Instantly check if your browser is leaking your real IP address through WebRTC — even when using a VPN or proxy. See every local and public IP your browser exposes.

🔒 100% private — this test runs entirely in your browser. We don’t log, store, or share your IP address or results.

🔍

Testing WebRTC…

Checking your browser for IP leaks via WebRTC STUN

Your Server IP (HTTP)

Detecting…

WebRTC Public IP

Checking…

WebRTC Local IPs

Gathering…

Leak Status

Analysing…

🌐 What is WebRTC?

WebRTC (Web Real-Time Communication) is a browser API for peer-to-peer video, audio and data. It uses STUN servers to discover your real IP — bypassing proxies and VPNs.

🔓 Why is it a privacy risk?

Even with a VPN active, WebRTC can expose your real public IP and local network IPs (192.168.x.x, 10.x.x.x) to any website that requests them via JavaScript — no permissions needed.

🛡️ Am I affected?

All major browsers (Chrome, Firefox, Edge, Safari) support WebRTC. If you use a VPN for privacy and your VPN doesn't block WebRTC, websites can see your real IP address.

✅ How to fix it

Disable WebRTC in your browser settings, use a browser extension like uBlock Origin (with WebRTC blocking enabled), or use a VPN that has built-in WebRTC leak protection.

How to Fix a WebRTC Leak

Chrome / Edge

Install the "WebRTC Network Limiter" extension from the Chrome Web Store, or go to chrome://flags and disable WebRTC for complete blocking. Better: enable uBlock Origin's WebRTC blocking in its settings.

Firefox

Type about:config in the address bar → search for media.peerconnection.enabled → set it to false. This completely disables WebRTC in Firefox.

Brave Browser

Go to Settings → Privacy and Security → WebRTC IP Handling Policy → select "Disable Non-Proxied UDP". Brave has built-in WebRTC protection.

Use a VPN with leak protection

ProtonVPN, Mullvad and ExpressVPN all have built-in WebRTC leak protection. Always check with this tool after connecting to confirm protection is working.

What Is a WebRTC Leak and Why It Exposes Your Real IP

WebRTC (Web Real-Time Communication) is built into every modern browser to power video calls, voice chat, and peer-to-peer file transfers without plugins. To connect two people directly, WebRTC has to discover your device’s real IP addresses — and it does this through a mechanism called STUN, which can bypass your VPN tunnel entirely. The result: a website can run a few lines of JavaScript and read your true public IP even while your VPN shows a different one. That is a WebRTC leak, and because it happens inside the browser, the VPN app often never sees it happen.

This test above queries your browser’s WebRTC interface the same way a tracking site would, then compares what it finds against your connection’s server IP. If your real address shows up where it shouldn’t, you’ll see it flagged instantly.

How to Test for WebRTC Leaks With a VPN (NordVPN, Surfshark, and Others)

The most reliable way to check whether your VPN actually stops WebRTC leaks is to test with the VPN on and compare the result to your real location:

Connect your VPN and pick a server in a different country.
Reload this page so the test runs fresh on the new connection.
Check the "WebRTC Public IP" result. If it shows your VPN’s IP (not your home IP), you’re protected. If your real IP appears, WebRTC is leaking around the tunnel.

NordVPNEnable the built-in Threat Protection or disable WebRTC via the NordVPN browser extension, then re-run this test to confirm the leak is closed.

SurfsharkSurfshark’s browser extension includes WebRTC blocking. Turn it on, reconnect, and verify here that only the Surfshark IP is exposed.

Other VPNsMany VPN apps don’t touch WebRTC at all — it’s a browser feature, not a network one. If yours doesn’t offer WebRTC protection, disable WebRTC in the browser itself (see the fix section above).

Key point most people miss: a VPN encrypts your network traffic, but WebRTC lives in the browser. Unless your VPN specifically blocks WebRTC (usually via its extension), the leak can slip past even a paid, well-configured VPN. Always confirm with a live test rather than assuming.

WebRTC Leak Test on Android and Mobile

WebRTC leaks affect phones too. On Android, Chrome and most Chromium-based browsers expose the same WebRTC interface as desktop, so a mobile VPN can still leak your real IP. To test on mobile, just open this page in your phone’s browser with your VPN connected — the test runs automatically and shows whether your real address is exposed.

Android (Chrome): there’s no built-in WebRTC toggle, so use a browser like Brave or Firefox, or a VPN app with WebRTC protection.
Firefox for Android: WebRTC can be disabled the same way as desktop (see fix section).
iPhone / Safari: iOS Safari exposes fewer WebRTC details, but testing with your VPN on is still the only way to be certain.

How to Disable WebRTC in Every Browser

If you’d rather block WebRTC entirely, here’s the quickest route per browser. Re-run the test above after each change to confirm it worked:

Brave: Settings → Privacy and security → WebRTC IP handling policy → "Disable non-proxied UDP". Brave makes this the easiest of any browser.
Firefox: type about:config → set media.peerconnection.enabled to false.
Chrome / Edge: no native toggle — use uBlock Origin’s "Prevent WebRTC from leaking local IP addresses" setting, or the WebRTC Network Limiter extension.
Safari: Develop menu → WebRTC → uncheck "Enable Legacy WebRTC API".

Disabling WebRTC will break video-calling sites (Google Meet, Discord in-browser, some conferencing tools). If you rely on those, a per-site approach or a VPN extension that blocks WebRTC selectively is a better balance than turning it off globally.

Frequently Asked Questions

Does a VPN protect against WebRTC leaks?

Not automatically. Most VPNs route your regular traffic through an encrypted tunnel but do not block WebRTC requests. Check your VPN provider's documentation for WebRTC leak protection, or verify with this test tool while your VPN is active.

What are local IP addresses?

Local IPs (like 192.168.x.x or 10.x.x.x) are your network addresses assigned by your router. WebRTC can expose these alongside your public IP, revealing that you're on a home network, office network, or VPN subnet.

Is WebRTC dangerous to keep enabled?

WebRTC itself is not malicious — it enables useful features like video calls. The risk is specifically the IP exposure. If you need WebRTC for services like Google Meet or Zoom, use a VPN with leak protection rather than disabling WebRTC entirely.

Why does the test show multiple IPs?

WebRTC gathers all available network interfaces: your VPN IP, your real public IP, your local/private IPs, and IPv6 addresses. Multiple IPs being shown is not automatically a leak — a leak occurs when your real public IP differs from your VPN IP.

How accurate is this test?

This test uses the same STUN-based technique that websites use to detect IPs. It is accurate for detecting standard WebRTC leaks. Some browsers or extensions may block STUN requests entirely, resulting in no IPs being detected — that is a safe result.