WebRTC Leak Test

Your browser’s WebRTC engine gathers your network addresses so calls can connect peer to peer, and any page can ask it to without a prompt. This test triggers that same collection and lists everything it hands over. If one of those addresses is a public IP that differs from the apparent one above while a VPN is on, your real address is leaking around the tunnel.

Reading your result

• Same as your apparent IP. Normal. WebRTC sees what every site sees.
• An address ending in .local. Good. Your browser masks local addresses with mDNS, as recent Chrome and Firefox do by default.
• A different public address. The leak this test exists to catch. Sites can read your real IP even with a VPN connected.

How to fix a leak

The clean fix is a VPN whose apps block leaks at the tunnel, so a browser quirk cannot route around it. VPNBaron passed this test in our hands-on review. The manual route is to disable WebRTC in your browser, at the cost of breaking in-browser calls.

Block leaks with VPNBaron →

More tools: What’s My IP · Privacy Check