WebRTC Leak Test
Inspect local IPs, public IPs, and mDNS hostnames from browser ICE candidates. Compare public addresses with the server-seen IP for possible VPN or proxy leaks.
When you run the WebRTC leak test, your browser may contact the listed Google and Cloudflare STUN servers to gather ICE candidates.
What does a WebRTC leak test check?
This free WebRTC leak test gathers browser ICE candidates and compares discovered public IPs with the IP seen by our server. It reports local addresses, public addresses, mDNS hostnames, and possible VPN or proxy mismatches. A result describes this browser session; it does not certify your VPN or test DNS leaks.
How to test for WebRTC IP exposure with a VPN
- Connect your VPN or proxy and confirm the expected public IP on the homepage. Keep that connection active during the test.
- Run the test. Your browser may contact the listed Google and Cloudflare STUN servers to gather ICE candidates; no camera or microphone permission is needed.
- Compare discovered addresses with the server-seen IP. Review mismatches and inconclusive results, adjust your VPN or browser WebRTC policy, then repeat in the same browser.
How to interpret the results
- Public IP mismatch
- A discovered public IP that differs from the server-seen IP in the same address family is flagged as a possible VPN or proxy leak. Cross-family differences are inconclusive because IPv4 and IPv6 can use different paths.
- Local IP or mDNS hostname
- A private IP exposes local network information, not your public location. An mDNS hostname can mask a local address; it does not prove that every network path is protected.
- No exposure observed
- The completed test found no flagged exposure in the available candidates. This is limited to the current session and cannot guarantee that your VPN prevents other types of leaks.
- Inconclusive
- Timed-out gathering, no useful candidates, or an unavailable server-seen IP prevents a reliable comparison. Repeat the test and review browser restrictions and connectivity.
Common Use Cases
- Run a WebRTC leak test after connecting to a VPN
- Check whether WebRTC exposes your real public IP
- Verify VPN protection isn't bypassed by WebRTC
- Check browser privacy settings and leak-blocking extensions
- Audit your privacy setup before sensitive browsing
- Debug video call connectivity issues
Technical references
Frequently Asked Questions
What is a WebRTC leak test?
A WebRTC leak test checks which local and public addresses a browser exposes through ICE candidates. This test uses the listed STUN servers and compares public candidates with the server-seen IP to flag possible VPN or proxy leaks. Missing candidates or different address families can make the result inconclusive.
What is a WebRTC leak?
A WebRTC leak occurs when browser connection discovery exposes an address your privacy setup was intended to hide. Exposure depends on browser policy, VPN routing, and available network interfaces. Seeing the VPN's public IP is expected; a different public IP requires investigation.
How do I prevent WebRTC leaks?
Use your VPN's documented WebRTC and IPv6 protection settings, and review your browser's WebRTC IP handling policy. Browser defaults and extension capabilities vary, so repeat the test after changes. Disabling WebRTC entirely can prevent browser calls from working; a passing test is not a guarantee against every leak.
Will disabling WebRTC break websites?
Disabling WebRTC may affect video conferencing (Zoom, Google Meet, Discord), voice calls in browsers, and some file sharing features. You can use selective blocking to allow WebRTC only on trusted sites.