Check if your browser leaks your IP through WebRTC

Your browser can expose your real IP address through WebRTC, even when you are connected to a VPN. This free test checks whether that is happening right now. No data is sent anywhere. Everything runs inside your browser.

Get protected with vpn.now Download the app

Free, with unlimited data. No card needed.

Browser WebRTC leak test showing IP address exposure

Running WebRTC test in your browser...

How to read these results

Public IP: The IP address the server sees. Should be your VPN server's IP if you are connected to a VPN.
WebRTC IPs (srflx): Public IPs found via WebRTC. A leak exists if any of these differ from your VPN IP and are not a local address.
Local IPs (host): Your private LAN address (e.g. 192.168.1.x). These are normal and cannot identify you from the internet.

What this test asks your browser to reveal

The page creates a temporary, empty WebRTC connection and reads the network candidates the browser offers for it. The connection carries no call, message, camera feed, or microphone audio. The test compares those candidates with the public IP returned by the normal web request.

Server-reflexive candidate

An srflx candidate is a public address discovered for the WebRTC path. If it differs from the VPN exit address and matches your normal connection, investigate it as a leak.

Host candidate

A host candidate is normally a private LAN address or an anonymized browser value. A private address alone does not identify your public internet connection.

Know the limits of one run

A browser may hide candidates, replace local addresses with temporary names, or expose different information after an update. A clean result covers this browser on this network at this moment; it does not inspect every installed app. Run the test once without the VPN and once with it, then compare the address values.

For the history of WebRTC, ICE and STUN, and why browser networking can reveal an unexpected route, use the separate WebRTC leak guide.

Secure your connection with vpn.now

vpn.now encrypts your traffic and replaces the public IP websites see. Free for everyone, with unlimited data and no card required. Native apps are available for Windows, macOS, Linux, and ChromeOS.

Create a free account Download the app

How to fix a WebRTC leak

Chrome / Edge / Opera

Chrome has no native toggle. Options:

Install the WebRTC Control extension to enable or disable WebRTC per site.
Install WebRTC Network Limiter (official Google extension) to restrict which network interface WebRTC uses.
Switch to Brave, which blocks WebRTC leaks by default in its fingerprint protection mode.

Firefox

Native fix available:

Type about:config in the address bar and press Enter.
Accept the warning.
Search for media.peerconnection.enabled.
Double-click it to set the value to false.

This disables WebRTC entirely. Re-enable it if you need browser-based video calls.

VPN client settings

Some VPN clients have a built-in setting to block WebRTC at the network level. Check your VPN app for any option labeled "WebRTC leak prevention", "block WebRTC", or "privacy controls". If your VPN client handles this, it will work across all browsers without needing per-browser changes.

After enabling any fix, return here and run this test again to confirm.

Retest after changing one setting

Change only one thing at a time so the next result tells you what worked. Keep the VPN server and physical network the same, apply the browser or VPN setting, close active call tabs, and press Run test again.

Record the normal public IP shown while the VPN is connected.
Check every public srflx result against that address.
If an unexpected public address remains, restart the browser and repeat.
If the result is clean, verify that a browser call still works if you disabled or restricted WebRTC.

A WebRTC result is only one layer

A clean browser result does not check DNS or the IPv6 route used by other software. Use the full VPN leak test for the combined browser checks, then follow the VPN verification checklist when testing a new app or network.

Related tools and guides

Full VPN Leak Test

IP address, WebRTC, and IPv6 exposure in one combined test.

IPv6 Leak Test

Check whether IPv6 is bypassing your VPN tunnel.

IP Address Lookup

Full details on your current public IP, location, and ISP.

WebRTC Leaks Explained

The full technical background on how WebRTC leaks happen.

Browser Fingerprinting

How sites track you beyond IP addresses.

Testing Your VPN

A complete guide to checking whether your VPN is working.

Frequently asked questions

Does this test send my IP address to vpn.now?

No. The WebRTC test runs entirely inside your browser using the browser's own API. No IP addresses are transmitted to our servers. The only network request this page makes is to load itself. Your results are calculated locally and displayed only to you. See our transparency page for everything we do and do not collect.

Is it normal to see local IPs like 192.168.1.x?

Yes, completely normal. Private LAN addresses (192.168.x.x, 10.x.x.x, 172.16-31.x.x) are the IP your router assigns to your device on your home or office network. They are not routable on the public internet and cannot be used by external sites to identify your location or ISP. Seeing them in these results is expected on any connected device.

My VPN is connected but I see an unexpected IP. What does that mean?

It means WebRTC bypassed your VPN tunnel and exposed a real IP. Whether that IP is your home IP or the VPN IP depends on your setup. If the IP shown belongs to your home ISP rather than your VPN provider, that is a confirmed WebRTC leak. Apply one of the browser-level fixes above, then run this test again to confirm the leak is closed.

Can WebRTC leaks be used to identify me even if I use a VPN?

Yes. If a website collects the IP that WebRTC exposes and that IP is your real home IP, they have a way to identify your actual internet connection. Combined with other tracking signals, this can be used to associate your VPN-browsing identity with your real identity. This is why fixing WebRTC leaks matters even if you are confident in your VPN. Read our article on being tracked while using a VPN.

Does disabling WebRTC break anything?

It breaks sites that depend on WebRTC for audio and video calls, including the browser versions of Google Meet, Zoom, Discord, and Jitsi. If you regularly use these in your browser, a smarter option is a browser extension that lets you disable WebRTC per site rather than globally. Alternatively, use the desktop apps for those services instead of the browser versions.

How often should I run this test?

Run it once after applying any fix to confirm it worked. After that, run it again whenever you install a browser update, change your VPN app, or switch to a new device. Browser updates sometimes change WebRTC behavior. VPN app updates can change how traffic is routed. One quick test takes less than ten seconds and removes any uncertainty. Also see our full guide to testing your VPN connection.

I passed the test. Does that mean my VPN is working perfectly?

It means WebRTC is not leaking your real IP in this browser. That is one important piece of the picture. A complete check also includes confirming your public IP matches your VPN server, and that your IPv6 address is not leaking. Use our full VPN leak test to cover all three at once.

Protect your connection with vpn.now

vpn.now encrypts your traffic and replaces the public IP websites see. It is free, with no credit card and no data cap. Native apps are available for Windows, macOS, Linux, and ChromeOS.