WebRTC Leak Test

What is a WebRTC leak? Check & fix it in under a minute

WebRTC enables real-time calling and screen sharing in the browser but its ICE candidates (connection details) can expose your public IP and sometimes local addresses. If these details leak outside your VPN, websites and advertisers can correlate sessions and geo-locate you. This page runs a fast WebRTC leak test and shows a clear PASS/FAIL so you know whether your VPN and browser are configured correctly.

How a WebRTC leak happens

When a page initializes WebRTC, the browser gathers network candidates using STUN/TURN and ICE. Without protection, those candidates may include your real WAN IP. Modern browsers mitigate this by using mDNS hostnames for local addresses, but public candidates can still appear if the VPN or firewall allows them. Learn more on MDN Web Docs.

How to read the results

• PASS (No leak): No public IP candidates are visible. Local addresses are hidden behind mDNS.
• WARN (Local exposed): Only private/lan candidates show. Turn mDNS on or block LAN in your VPN.
• FAIL (Public IP exposed): Your real IP appears in candidates treat as a leak and fix immediately.

Quick fixes that work

• Keep mDNS enabled: Default in Chromium and Firefox; it masks local IPs with hostnames.
• Harden your VPN: Use private DNS, enable "Block LAN" (if available), and prefer WireGuard.
• Browser controls: Disable WebRTC via a privacy extension, or restrict it per-site. Consider strict tracking protection and a reputable blocker (uBlock Origin).
• Retest after changes: Re-run this WebRTC leak test, then confirm with our DNS Leak Test, IP Check, and Browser Privacy Check.

Need a provider that passes?

If your current setup keeps leaking, review our vetted options in the best VPNs for privacy & streaming section. Look for independent audits, RAM-only servers, and consistent WebRTC/DNS leak protection.