Is a LAN IP in the result a leak?

No. Private ranges like 192.168.x.x or 10.x.x.x are local only and can't identify you externally. Only a public IP is a real leak.

Should I disable WebRTC entirely?

If you never use browser calls, blocking it is the safest option. Otherwise use leak protection so calls still work.

Does this work on mobile?

Yes — mobile browsers run WebRTC too. The test works the same way.

How to check for a WebRTC leak

WebRTC powers in-browser calls — and can quietly hand a website your real IP address, even when you're connected through a VPN.

Tool: Browser fingerprint Try it now — free, no signup. Open →

What it is

WebRTC lets browsers do real-time audio, video and file transfer without plugins. To connect two peers directly, the browser collects candidate IP addresses — including your local network IP and sometimes your real public IP.

A web page can read these candidates with a few lines of JavaScript, no permission prompt required.

Why it matters

If you use a VPN for privacy, a WebRTC leak can expose the very thing you're hiding: your real public IP. That links your “anonymous” session straight back to your home connection.

How to check

Open the tool above and look at the WebRTC result. It lists the candidate IPs your browser exposes and flags any that are public (an outward leak) versus LAN (local only, not a leak).

How to fix

Use a VPN or extension with WebRTC leak protection.
In Firefox set media.peerconnection.enabled to false; in Chrome use a reputable WebRTC-control extension.
Disable IPv6 if it isn't tunnelled.
Re-test to confirm only LAN candidates remain.