Skip to content
iplogs.comSign up
Guide · Last updated 2026-11-19

Why complete VPN blocking can't be a compliance solution

Nobody has a blocklist of every VPN IP, and nobody can build one. Providers rotate exits all the time. Residential proxies are indistinguishable from consumer broadband at the IP level, and bypass protocols disguise VPN traffic as ordinary HTTPS. Even so, treating VPN detection as a boolean and shipping a static blocklist is a common way for engineers to try to meet a compliance requirement. This guide explains why it fails and what works better.

By Fizzah Mehtab ·

Why can't you block every VPN?

No complete VPN blocklist exists, because three things defeat it. Commercial providers rotate and re-IP their exits, so a static list goes stale soon after it is compiled, which misses current servers and blocks addresses already handed to ordinary customers. Residential proxies exit through real consumer connections on genuine ISP networks, so an ASN check classifies them as residential and lets them through. Anti-censorship protocols such as REALITY, Xray and AmneziaWG make VPN handshakes look like ordinary TLS traffic. The workable alternative is a graded verdict with per-action policy. Block high-risk writes such as signup, payment, KYC and admin on vpn_detected, step up authentication on vpn_likely, raise scrutiny on suspicious, and leave read traffic open. Keep every contributing signal, so iCloud Private Relay and Cloudflare WARP can follow separate rules. Publish the error rate: IPLogs measured 0.4% wrong flags on 1,043 addresses. No detector can guarantee a user's physical location against a well-configured VPN.

The blocklist problem

Any commercial VPN of real size runs thousands of exit IPs. Several providers publish their own server lists, and community aggregators compile tens of thousands of CIDRs for the rest. Those lists go stale within hours of being scraped. New servers come online, old ones rotate out, and providers re-IP their fleets, partly for performance and partly to stay ahead of censors.

Ship a quarterly “known VPN” CIDR list with a 403 rule and you get two failures at once. Most current VPN traffic gets through, while IPs the providers have already released to other customers get blocked. Users notice both, and both turn into support tickets.

Residential proxies defeat ASN classification entirely

The residential-proxy business (Bright Data, Webshare, Oxylabs, IPRoyal, NetNut and others) resells real consumer broadband connections, recruited through SDKs in mobile apps, browser extensions, and compromised devices. Because the exit IP sits on a genuine ISP ASN such as Comcast, BT, Deutsche Telekom or Reliance Jio, an ASN-based detector returns “residential”, and many commercial classifiers let the request through.

The recent FBI/Europol takedown of SocksEscort reported 369,000 compromised devices across 163 countries. Compromised home devices like these sit on consumer ASNs and pass an ASN-only check. Catching them takes backbone-reputation signals, vendor gateway lists, and behavioural heuristics, such as an RTT mismatch or one user-agent appearing in several geos, on top of ASN classification.

There is more on this in residential vs datacenter IPs, and a short definition in the glossary.

Anti-censorship protocols evolve faster than blocklists

REALITY, Xray, and AmneziaWG exist precisely to defeat protocol-level detection. They make VPN handshakes look like ordinary traffic, typically TLS to common services, so a deep-packet-inspection blocklist that flags “VPN protocols” misses them. This area moves quickly, and the REALITY / Xray / AmneziaWG breakdown covers where it stands now. A blocklist compiled six months ago may already be behind protocols built specifically to evade it.

What actually works: graded verdicts and per-action policy

Stop treating “is this a VPN” as a yes/no question. A workable policy uses tiered verdicts and sets different rules for each kind of action:

VerdictRead trafficWrite / payment / signup
vpn_detectedAllowBlock, step up to strong auth, or require verification
vpn_likelyAllowStep up auth; require 3DS on payment; queue for review
suspiciousAllowTreat as elevated risk; require email verification
cleanAllowStandard flow

For this to work, the verdict has to arrive with every signal that contributed to it, so policy can treat each kind of evidence differently. Apple Private Relay and Cloudflare WARP, for example, are not commercial VPNs and shouldn't share their policy. The false-positive rate also has to be measured in the open. Ours is published at /accuracy so the trade-off can be audited.

A note on compliance framing

Some jurisdictions have proposed or passed rules that in effect require websites to verify a user's physical location even when that user is on a VPN. Whether a rule like that can be met technically is a separate question from whether it can be enforced against you. Before acting, check the current text of the statute against an authoritative source: your counsel, the statute itself, or organisations such as the Electronic Frontier Foundation and Access Now. On the technical side, no detection layer can guarantee physical location against a determined, well-configured user.

FAQ

Is it possible to block every VPN IP?

No. Commercial providers rotate exits constantly, so any static blocklist starts going stale within hours of being compiled. On top of that, anti-censorship protocols disguise VPN traffic as normal TLS, and residential proxies run on real consumer ISPs, where they look exactly like ordinary home users.

Why don't ASN-based blocks catch residential proxies?

The exit is a real consumer device on a real consumer ASN. The IP belongs to Comcast, BT or Deutsche Telekom, the same networks your legitimate users come from. ASN classification was designed to flag datacenter traffic, and nothing in it separates a paying customer from a home connection that has been rented out.

If complete blocking fails, what should I do instead?

Work with a graded verdict instead of a yes/no answer. On confirmed VPN exits, block high-risk writes (signup, payment, KYC, admin). On weaker signals, step up authentication, and leave read traffic alone. Keep the multi-source provenance so your policy can treat each signal type differently.

How do compliance rules like age verification interact with VPN use?

The specifics vary by jurisdiction, so check the current text against an authoritative source: your counsel, the relevant statute, or organisations such as EFF and Access Now. On the technical side, no detection layer can guarantee a user's physical location once they are on a well-configured VPN or residential proxy. Blocking VPNs to meet a 'physical location' requirement misses the bypass traffic and still hurts legitimate privacy users.

Does multi-signal detection have a measurable false-positive rate?

It should. IPLogs publishes a 0.4% false-positive rate against an ASN-validated ground-truth corpus at /accuracy. A vendor that won't share its error rate on a labelled corpus is asking you to trust a number you can't audit.

The accuracy benchmark is at /accuracy and the implementation walkthrough at detect-vpn-users. For a side-by-side with other IP-intel APIs, see /compare/vpn-detection-apis.