YourTools.
简体中文
Back to the catalog
Tools

WebRTC leak test

Check whether WebRTC reveals a public IP address other than the one websites see, such as your real address behind a VPN or proxy, or your local network address.

Loading…

Your browser sends a request to public STUN servers run by Google, Cloudflare and Twilio, which see your IP address as any website does. The addresses found are looked up on this site’s server for their location and network and are not stored.

About this tool

Check whether WebRTC, the browser feature behind video calls, reveals an IP address other than the one websites see. Behind a VPN or proxy, a WebRTC leak hands any website your real public address. The test also shows whether your local network address, such as 192.168.1.20, is visible.

The test runs as soon as the page opens. Your browser asks public STUN servers run by Google, Cloudflare and Twilio for its address, the same way any page’s script could, and the page compares every public address found with the one this site’s server sees. Addresses that differ are looked up for their location and network (ASN) and are not stored.

How to use it

  1. Connect your VPN or proxy the way you normally use it, then open the page.
  2. Wait a few seconds while the browser contacts the STUN servers.
  3. Read the result: “No leak” in green, or “Leak” in red with the addresses that differ.
  4. Check the table: the address websites see, then what each STUN server returned, with location and network.
  5. After changing a setting or switching servers, select “Test again”.

Common questions

What is a WebRTC leak?

WebRTC lets browsers connect directly for calls and file transfers. To do so it asks a STUN server which public address it appears from, and any page can start that request without asking you. Many VPNs and proxies carry only ordinary web traffic, so the request can leave through your normal connection and reveal your real address.

How do I stop a WebRTC leak?

Turn on your VPN app’s WebRTC or leak protection, or use its system-wide (TUN) mode so that all traffic goes through it. In Firefox you can set media.peerconnection.enabled to false in about:config; in Chrome and Edge an extension such as WebRTC Network Limiter keeps WebRTC on the proxied connection. With WebRTC off, video calls in the browser may stop working.

Why does it show my IPv6 address but say there is no leak?

When the other addresses WebRTC shows belong to the same network (the same ASN) as the address websites see, such as the IPv6 address of the same internet provider, they do not reveal a different connection. If a VPN should hide IPv6 too and WebRTC shows another provider’s IPv6 address, that is reported as a leak.

What does “No public address” mean?

That STUN server did not answer, usually because the browser, an extension, a firewall or the VPN blocks WebRTC’s UDP requests. Without an answer, WebRTC reveals nothing through that server.

Is my local IP address exposed?

Current browsers hide local addresses behind a random name ending in .local, and the page says so. If a local address such as 192.168.1.20 is shown, sites can use it to tell devices on the same network apart.

Is anything stored?

No. The STUN servers see your address as any website does. The addresses found are sent to this site’s server only to look up their location and network, and are not stored.