What "VPN detected" actually means
This checker looks at the public IP your connection presents and asks a simple question: is this address in a database of known VPN, proxy, or datacenter ranges? If it is, you'll see it flagged. That flag is how streaming services and some websites decide you're on a VPN and choose to block or challenge you.
A "detected" result isn't a problem for privacy — it means the site can tell you're using a VPN, but it still can't see who you are or where you really are. A "not detected" result is more nuanced than it sounds: it can mean the VPN's IP simply isn't in the database yet, that you're on a residential VPN routing through real home addresses, or — the case to watch for — that your real IP is showing because of a leak. The way to tell them apart is to check whether the ISP shown is your VPN provider or your home internet company.
Why a VPN can still leak your real IP
Turning a VPN on doesn't guarantee every request goes through the tunnel. The classic failure is a DNS leak: your traffic is encrypted, but the domain lookups that translate site names to addresses slip out through your ISP's resolver, so your ISP (and anyone watching it) can still see which sites you visit. Good VPNs route DNS through the tunnel and advertise "DNS leak protection" — worth confirming it's enabled in the settings.
WebRTC leaks are sneakier. WebRTC is a browser feature for real-time audio and video, and it can reveal your real IP directly to a web page, bypassing the VPN at the browser level. Because it happens in the browser rather than on the network, a server-side check like this one can't see it — you test for it with a dedicated WebRTC leak tool or by disabling WebRTC in your browser. Finally, if your kill switch isn't on, a dropped VPN connection silently reverts you to your normal IP without warning, and IPv6 traffic can escape a tunnel that only covers IPv4.
How to verify your VPN is working
Run through this quickly whenever you want to be sure. First, note your real IP and ISP with the VPN off (reload this page). Then connect the VPN and reload: the IP should change and the ISP should now be the VPN provider or a datacenter, not your home internet company. If the ISP still shows your home provider, you have a leak — check that the VPN actually connected and that its kill switch is on.
Next, run a dedicated DNS leak test and a WebRTC leak test — those cover the two paths this server-side check can't see. If all three agree (new IP, DNS through the tunnel, no WebRTC exposure), your VPN is doing what it's supposed to. It's worth repeating the check occasionally, since an app update or a settings change can quietly turn protection off.
How to choose a VPN, if you decide you need one
A VPN is a tool, not a magic privacy button, and the right one depends on what you're actually trying to do — stream region-locked content, avoid snooping on public Wi-Fi, or just reduce how easily you're profiled. A few things are worth looking for regardless. An independently audited no-logs policy matters more than marketing claims; a published third-party audit is the difference between "we promise" and "someone checked." The provider's jurisdiction affects what it can be compelled to hand over.
On the technical side, modern protocols like WireGuard are fast and well-regarded; built-in DNS leak protection and a reliable kill switch are close to essential; and support for the number of devices you actually use saves money. Speed and server locations matter if you're streaming. Free VPNs deserve real caution — running a VPN network costs money, and when you're not paying, the business model is often selling the very data you're trying to protect. If you already use a VPN, use the checker above to confirm it's genuinely masking your IP, not just showing a "connected" badge.