VPN Connection Checker
See exactly what the internet sees about your connection — public IP, geolocation, ISP, and whether your IP looks like a VPN, proxy, or datacenter address. Includes a WebRTC leak test that runs in your browser.
Checking your connection…
WebRTC Leak Test
Public IPs leaked via WebRTC
✓ None — your VPN (if any) is correctly tunneling WebRTC.
What we send where: Your public IP (which every site sees automatically) is forwarded to ip-api.com for geolocation and datacenter classification. The WebRTC leak test runs entirely in your browser and connects to Google's public STUN server (stun.l.google.com) — those local IPs never reach our backend.
What we store: Nothing. No logs, no database writes, no cookies. Each check is one-shot.
How VPN detection works:We match your IP against datacenter ranges and known VPN provider org names. A “likely VPN” verdict means your IP signals match a VPN/proxy. False negatives are possible — small VPNs can blend in with regular ISPs.
Frequently asked
How accurate is the VPN / proxy detection?
Probabilistic. We match your public IP against three signals: datacenter / hosting-provider ranges (most VPN exits run on AWS, OVH, Hetzner, etc.), known VPN-provider AS numbers, and the ASN organization name. When all three flag, "likely VPN" is confident. Small or residential-IP VPN providers can blend in with normal ISPs, so a "no VPN detected" result is not a guarantee.
My VPN is on but the checker says I'm not using one. Why?
Two common reasons. (1) The VPN provider routes your traffic through residential proxies (a paid feature for some providers) — those look like normal home connections, by design. (2) The provider just hasn't been catalogued in ip-api.com's classification yet. The WebRTC section below is a more reliable test: if it shows IPs from a different network than the public IP we report, your VPN is masking your real address even if the org-name detection misses.
Will my employer or ISP see that I ran this check?
We store nothing. No logs, no database writes, no cookies. The check is one-shot per page load and the result lives only in your browser tab. That said, your network operator can still see the TLS-encrypted connection to statusdetector.com in their flow logs — they just won't see anything specific about what page you loaded or what the result was.