WebRTC IP Leak Test

WebRTC can reveal your real public IP and local network addresses, even behind a VPN. This test probes multiple STUN servers from your browser and compares what it finds with the IP our server sees.

IP our server sees (HTTP request)
216.73.216.145
This is the address carrying your HTTP connection — your VPN exit node if you use one.
WebRTC-discovered public IP (STUN)
— run test —
Discovered by your browser asking a STUN server "what IP do you see?" — ignores some VPNs.
Test runs entirely in your browser — no data is stored.
How to read these results
No leak
The WebRTC public IP matches the IP our server sees — either you aren't using a VPN, or your VPN fully intercepts WebRTC traffic.
WebRTC leak
WebRTC is reporting a public IP different from your HTTP IP. If you're on a VPN, it is leaking your real ISP address. Consider a VPN client with a built-in WebRTC kill-switch, or disable WebRTC in your browser.
Local IPs visible
Your browser exposed raw private-range IPs (e.g. 192.168.x.x). Modern browsers usually hide these behind mDNS .local hostnames by default — raw IPs suggest an older browser or a policy override.
No candidates
WebRTC is disabled, blocked by an extension, or the network is preventing STUN — that's a good privacy posture for some threat models, but may break Zoom/Meet/Discord calls.