toolcrate
All tools →
📡 checked directly in your browser — no third party sees your IP through this tool

WebRTC Leak Checker

WebRTC can expose your real IP address even when you're behind a VPN, because it talks to a STUN server directly, bypassing some VPN tunnels. Most "leak test" sites are themselves third parties logging your IP to show it to you - this one talks to a public STUN server directly from your browser and only ever displays the result to you.

How it works

The check opens a real RTCPeerConnection to a public Google STUN server and reads back the ICE candidates the browser gathers for it — those candidate strings contain whatever IP address WebRTC would use to set up a peer connection, which this tool parses directly and classifies as private, public, or a browser-obscured local address, rather than asking a third-party leak-test site to look it up for you.

FAQ

What does a ".local" address in the results mean?
It means your browser's mDNS privacy protection is working — Chrome, Firefox, and Edge now replace your real local IP in ICE candidates with a random UUID plus .local, so it isn't a parseable IP and isn't a leak.
If I'm using a VPN, what public IP should I expect to see?
The public IP found via the STUN request should match your VPN provider's IP, not your ISP's — if it instead shows your real ISP-assigned IP, that's exactly the WebRTC leak this checks for, since WebRTC can reach a STUN server directly and bypass some VPN tunnels.

Free, unlimited, no account. If this saved you a paid tool, a small thanks is appreciated.

Say thanks — $3