Compute network, broadcast, mask and first/last host for IPv4 and IPv6, test IP membership and convert ranges to CIDR
Privacy Leak Checker
Check whether your VPN leaks your address: WebRTC leaks (ICE candidates), IPv6 leaks, time zone and language mismatches with the IP country and the navigator.webdriver flag, with the limits of the check explained.
Workspace
How the result is calculated
WebRTC: an RTCPeerConnection is created with a STUN server and ICE candidates are collected; an srflx candidate with a public address that differs from the address the server saw (ipify) = a leak, a host candidate with a public address = a warning, and .local (mDNS) candidates mean good masking. IPv6: if both IPv4 and IPv6 exist and their countries (ipwho.is) differ, IPv6 may bypass the VPN. Time zone: a difference ≥ 30 minutes between the browser offset and the IP zone’s offset. Language: the IP country’s region is absent from navigator.languages regions (info only). Automation: navigator.webdriver.
Limits:
It does not detect DNS leaks (that needs a DNS server under our control), IP reputation or the full browser fingerprint. “No problems” does not mean your connection is fully anonymous. The check contacts ipify, ipwho.is and a STUN server (Google’s public one by default) and these services see your address. WebRTC depends on the browser (it may be disabled). A time-zone mismatch is weak evidence and may be legitimate (travel). I did not test the live check on a real VPN.
FAQ
Does it detect DNS leaks?
No; that needs a dedicated server.
What if WebRTC leaks?
Disable WebRTC, use an extension that blocks it, or a VPN that closes the leak.
