myaddress.is

Privacy tool

WebRTC leak test

WebRTC lets browsers talk to each other directly — and in doing so it can reveal an IP address your VPN was meant to hide. This test runs live in your browser, right now.

WebRTC local IP
probing…
Public IP (from edge)
216.73.217.14
Verdict
running test…

What you're seeing

If a local IP appears above (something like 192.168.x.x or a long fe80:: address), your browser is exposing your device's address on its own network through WebRTC. On its own that's low-risk. The real concern is when your public WebRTC address differs from the IP your VPN shows — that means sites can see around your VPN to your true address.

How to stop the leak

The cleanest fix is at the browser: disable WebRTC where you don't need it, or install an extension that blocks WebRTC IP handling. A VPN with built-in WebRTC leak protection closes it too. If you rely on video calls, don't disable it globally — use a per-site approach instead so calls keep working.

Frequently asked questions

Is a WebRTC leak dangerous?
A leaked local IP alone tells a site little. It matters most to people using a VPN for privacy: if your real public IP leaks through WebRTC, the VPN isn't giving you the anonymity you expect. For everyone else it's mostly informational.
Why does this show an address even without a VPN?
WebRTC surfaces your local network address by design, so browsers can set up direct connections for calls and file transfer. Seeing your 192.168.x.x here without a VPN is normal, not a breach.
Does disabling WebRTC break anything?
It can stop browser-based video calls and some peer-to-peer features from working. Blocking just the IP-exposing part — rather than WebRTC entirely — usually keeps calls working while closing the leak.

Runs client-side. No server needed — the probe uses your browser's own WebRTC stack. FAQ ships as FAQPage schema; page carries SoftwareApplication + BreadcrumbList.

← back to myaddress.is