WebRTC leak test

WebRTC is a browser feature that can reveal your real IP even while a VPN is connected. This test runs in your browser and shows what it exposes.

Addresses exposed via WebRTC:
  • testing…

How to use the webrtc leak test

  1. Open this page — the WebRTC test runs automatically.
  2. Read the list of exposed addresses.
  3. If a public IP appears while on a VPN, fix the leak with the steps below.

How to read this

Local addresses (like 192.168.x.x or an mDNS .local name) are harmless — that's your home network. A public address that matches your real IP means WebRTC is leaking around the tunnel.

How to fix a WebRTC leak

  • Use a browser extension that disables or limits WebRTC.
  • In Firefox, set media.peerconnection.enabled to false in about:config.
  • Use a VPN app with built-in leak protection.

Code & API examples

Use this from the command line or your code.

Browser only
// WebRTC runs in the browser; there is no server-side equivalent.
console.log(new RTCPeerConnection());
Check your public IP instead
curl ifconfig.me

See all endpoints at /api/tools/.

Frequently asked questions

WebRTC can gather your local and public IP addresses for peer-to-peer connections. A page can read them via JavaScript, revealing your real IP around a VPN.

Use a browser extension that disables WebRTC, set media.peerconnection.enabled to false in Firefox, or use a VPN app with built-in leak protection.

WebRTC asks your operating system directly for network addresses to set up peer connections, sidestepping the browser's normal proxy and routing. That can surface your real IP independent of the tunnel.

A local IP (like 192.168.x.x) reveals your internal network layout and is mostly a fingerprinting signal. A public IP leak exposes your actual address to the site — that's the serious one around a VPN.

Not necessarily. Video calls and conferencing rely on it. The goal is to stop it leaking your real public IP — many tools restrict WebRTC to the VPN interface rather than killing it outright.

Chrome, Edge, Firefox, and other WebRTC-enabled browsers can all leak. The exact behavior and the fix differ per browser, so test each one you use rather than assuming.

Yes. Mobile browsers support WebRTC and can leak just like desktop. If your VPN runs as a full-device tunnel, the leaked address is usually the exit IP anyway, but you should still verify.

The setting may not have applied, an extension may be re-enabling it, or a different browser is being tested. Some flags only block public IPs while still exposing the local one — re-check after a full restart.

No. If the address shown matches your exit hole and not your real IP, there's nothing to fix — that's the expected result when your VPN tunnels WebRTC correctly.

The detection runs in your browser using the same WebRTC APIs a tracking site would. We display what's exposed so you can act on it; the result isn't logged or tied to you.

Some do — privacy extensions and uBlock Origin can restrict WebRTC. Coverage varies, so don't assume; run this test with your extensions active to confirm they're actually working.

When the whole device is tunneled, WebRTC can only reach the network through the hole, so it surfaces the exit IP rather than your real one. Generating keys client-side and routing all traffic through the tunnel keeps WebRTC inside it.
Related tools
Is my VPN working? Browser fingerprint test IPv6 leak test
Want to hide your IP for real?

vpn.golf is a no-logs WireGuard VPN. Pick a hole, take the shot.

Step up to the tee — free