WebRTC leak test

Is your browser leaking your real IP?

WebRTC is a browser feature used by video calls and screen-shares. It also reveals network addresses that can bypass a VPN if your browser doesn't have leak protection turned on. This page checks what your browser exposes.

— running test… collecting ICE candidates…

Your apparent public IP (from /api/lookup)

From server looking up…This is what every web request shows. If you're behind a VPN, it should be your VPN's IP — not your real one. —

Public IPs WebRTC revealed If any of these don't match the row above, that's a leak.

Collecting…please wait—

Local network addresses (not usually a privacy issue) RFC 1918 addresses or mDNS hashes — mostly harmless.

Collecting…please wait—

How this test works: we create an RTCPeerConnection in your browser and ask it to gather ICE candidates — the network endpoints a video-call peer would use to reach you. The browser dumps these candidates into the page. We parse them and compare any public IPv4/IPv6 addresses against the public IP your server sees. If they don't match, your browser is exposing a route that bypasses whatever's in front of you.

If you see a leak: a VPN alone doesn't fix WebRTC leaks. You need either a privacy-focused browser (Brave and Tor handle this), a browser extension that blocks WebRTC peer connections (uBlock Origin → Settings → "Prevent WebRTC from leaking local IP addresses"), or both. See our recommended privacy browsers.

Modern browsers often mask local IPs with mDNS hashes (those long .local strings). That's normal and means your browser has a privacy guard turned on for the local network. Public-IP leakage is the actual concern.