WebRTC leak test: what your browser gives away

WebRTC is a browser feature for real-time audio, video, and data. To connect peers it gathers your IP addresses — and a website can read them with simple JavaScript. If it exposes your real public IP while a VPN is on, that's a WebRTC leak: the site sees who you are even though your VPN is connected.

It opens a peer connection to public STUN servers and collects the ICE candidates your browser produces, then parses the IP addresses out of them. Everything runs locally in your browser — the candidates are shown to you and never sent to us. Press Re-run test any time to check again.

Most desktop VPN apps route your traffic but don't stop the browser from gathering IP candidates over WebRTC, so your real public IP can still leak. Browser-based VPNs that handle WebRTC — like Zippa's Chrome extension — prevent this because they control the browser's networking directly.

It's a good sign. Modern browsers hide local addresses behind mDNS (".local") and may not return a public candidate without a leak. But results vary by browser, network, and extensions, so it's worth re-testing on public Wi-Fi and with your VPN on and off.

No. Zippa is built to prevent WebRTC leaks in Chrome, so sites see the location you picked instead of your real IP. Combined with our strict no-logs policy, your real address stays private on both fronts.

It depends who runs it. Plenty of free VPNs pay their bills by logging and selling browsing data — that's the real catch. Zippa is funded by people who upgrade to Premium, not by your data, and we keep a strict no-logs policy, so there's nothing to record or sell in the first place.