Account

What new tool do you want?

Security & Privacy

WebRTC Leak Test (VPN Check)

Check whether WebRTC exposes your real or local IP address while using a VPN — see every ICE candidate your browser reveals.

How to use

  1. 1Connect to your VPN, then press Run test.
  2. 2If a public IP that isn't your VPN's appears, WebRTC is leaking — disable it or use your VPN's leak protection.

How it's calculated

The page opens a WebRTC connection to a public STUN server and lists the addresses your browser offers. Modern browsers hide local IPs behind random .local names.

Frequently asked questions

What is a WebRTC leak?

WebRTC (used for video calls) can reveal your real IP address to websites even when you're on a VPN.

How do I fix a leak?

Turn on your VPN's WebRTC leak protection, use a browser extension that limits WebRTC, or disable it in Firefox (media.peerconnection.enabled).

Does this test contact a server?

Only a public STUN server (Google's), which tells your browser its public address. Results aren't stored or sent to us.

Why a video-calling feature can expose your real IP

WebRTC lets two browsers connect directly to each other for things like video calls, which means each side needs to learn the other's real network address — a VPN, by contrast, is designed to hide that address from everyone except the VPN server. The two features serve opposite goals, and WebRTC's address-discovery step (ICE candidate gathering) runs independently of your browser's regular HTTP traffic, so a VPN that only reroutes normal web requests can leave this specific channel untouched. The test works by opening a real WebRTC connection to a public STUN server and listing every network address your browser was willing to hand over during that handshake.

Reading the candidate types the test reports

Candidates of type "srflx" (server-reflexive) are your public IP as seen from outside your network — exactly what a website could use to identify you even through a VPN. Type "host" candidates ending in ".local" are local IPs that modern browsers have already hidden behind a randomly generated mDNS name specifically to prevent this kind of leak; type "host" candidates that resolve to a real private-range address (10.x, 192.168.x, 172.16–31.x) mean your local network IP is exposed in the clear, which current Chrome and Firefox normally prevent by default.

What counts as an actual leak vs. expected behavior

Seeing a public IP in the results isn't automatically a leak — if it matches the IP your VPN app shows you, that's the VPN's own exit address working as intended through WebRTC, same as it would through a browser tab. It's only a leak if the srflx address differs from your VPN's address, meaning the STUN handshake bypassed the VPN tunnel entirely and reached the internet through your normal connection instead. That comparison is something only you can make — the test can't know what your VPN's IP is supposed to be, so it just shows you what WebRTC actually revealed.

If you find a leak

Most VPN apps have a dedicated WebRTC leak-protection toggle in their settings now, which is the first thing to check. Failing that, Firefox lets you disable WebRTC outright by setting media.peerconnection.enabled to false in about:config, and several ad-blocker extensions include a WebRTC-blocking option — both trade away video-calling-in-browser functionality for the privacy guarantee.

Related tools

More: Security & Privacy