WebRTC Leak Test

Check whether WebRTC reveals an IP address different from the one websites see. STUN requests often travel outside a proxy tunnel and expose your real public IP or your local network address.

Testing WebRTC…

Gathering ICE candidates from each STUN server.

0/9 STUN servers finished

Your connection

IP address
Checking…
ISP
Checking…
Country
Checking…

Results by STUN server

Each server is asked in its own WebRTC connection. The public IP is the address that STUN server saw your browser connect from.

Google

stun:stun.l.google.com:19302

Checking
Public IP
Checking…
Local IP
Checking…
mDNS hostname
Checking…

Google 2

stun:stun2.l.google.com:19302

Checking
Public IP
Checking…
Local IP
Checking…
mDNS hostname
Checking…

Cloudflare

stun:stun.cloudflare.com:3478

Checking
Public IP
Checking…
Local IP
Checking…
mDNS hostname
Checking…

Twilio

stun:global.stun.twilio.com:3478

Checking
Public IP
Checking…
Local IP
Checking…
mDNS hostname
Checking…

Nextcloud

stun:stun.nextcloud.com:443

Checking
Public IP
Checking…
Local IP
Checking…
mDNS hostname
Checking…

STUNTMAN

stun:stunserver.stunprotocol.org:3478

Checking
Public IP
Checking…
Local IP
Checking…
mDNS hostname
Checking…

Syncthing

stun:stun.syncthing.net:3478

Checking
Public IP
Checking…
Local IP
Checking…
mDNS hostname
Checking…

Xiaomi

stun:stun.miwifi.com:3478

Checking
Public IP
Checking…
Local IP
Checking…
mDNS hostname
Checking…

Tencent QQ

stun:stun.qq.com:3478

Checking
Public IP
Checking…
Local IP
Checking…
mDNS hostname
Checking…

Frequently asked questions

What is a WebRTC leak?

WebRTC lets browsers make real-time audio, video and data connections. To find a route between peers it asks STUN servers which address you connect from. Those requests often bypass the proxy or VPN, so any website can read your real public IP with a few lines of JavaScript.

How does this test work?

We open a WebRTC connection to each of nine public STUN servers and collect the ICE candidates your browser produces. Server-reflexive addresses are compared with the IP this page arrived from — exactly for IPv4, and by /64 network for IPv6, because IPv6 privacy addresses rotate within the same network.

Is an exposed local IP a problem?

A private address such as 192.168.x.x does not locate you, but it narrows down your device and network. Modern browsers replace it with a random .local mDNS hostname; seeing a real local address means that protection is off.

How do I stop WebRTC leaks?

Use a VPN that tunnels UDP and IPv6, or set WebRTC to use the proxy IP in your anti-detect browser. In Firefox you can turn off media.peerconnection.enabled; in Chromium browsers an extension or the WebRtcIPHandling policy can restrict WebRTC to the proxied interface.