WebRTC Leak Test — Does WebRTC Expose Your Real IP?

How to use

1. Press Run leak test (avoid toggling your VPN mid-test).
2. Compare the HTTPS IP row with the WebRTC candidate list.
3. Read the verdict: a match means leak for VPN users; different or none means protected.
4. Toggle your VPN or extension and press Retest to confirm the fix.

About this tool

VPNs are great until a browser feature quietly bypasses them — WebRTC is the classic offender. This test opens a real RTCPeerConnection, asks Google's public STUN server what address it sees, and lists every public (srflx or relay) candidate your browser is willing to reveal. It then fetches your normal HTTPS exit IP from the ipify echo service and compares the two. If the addresses match while you are on a VPN, websites can read your true address with a simple script — that is a WebRTC leak. If WebRTC reports nothing or a different address, your tunnel covers voice and video traffic too. The verdict panel spells out each pattern in plain English, and the retest button lets you verify after toggling your VPN. Only these two keyless, anonymous requests are made, and nothing is stored.

FAQ

Rate this tool

Your rating stays in this browser (local storage) — nothing is sent to any server.