Proxy, VPN & residential proxy database

Every open proxy, Tor exit node, datacenter IP, commercial VPN, and residential proxy - in a single file. Enterprise delivery. Hourly updates. IPv4 + IPv6.

Built for enterprise and high-volume deployments.

What's included

  • Open proxies (HTTP / SOCKS)
  • Tor exit nodes
  • Datacenter IP ranges
  • Commercial VPN endpoints
  • P2P residential proxy IPs
  • IPv4 + IPv6

Common use cases

  • End-to-end fraud defense across all proxy classes
  • Account takeover and credential stuffing
  • Bot, scraper, and ad-fraud filtering
  • Ticket and sneaker bot defense
  • One integration covering every proxy class

Schema

cidr,asn,isp,countryCode,countryName,block,proxyType_residentialProxy
8.8.8.0/24,15169,GOOGLE,US,United States,1,0
24.0.0.0/32,7922,COMCAST-7922,US,United States,1,1
2606:4700::/32,13335,CLOUDFLARENET,US,United States,1,0
2001:558::/64,7922,COMCAST-7922,US,United States,1,1

Same six columns as the standalone databases plus a seventh: proxyType_residentialProxy (0 or 1), which becomes a nested proxyType.residentialProxy boolean in the MMDB. Lets one lookup tell residential proxies apart from datacenter / VPN / Tor entries when your downstream rules need to.
block=1 - high-confidence proxy of any class.
block=2 - suspicious, lower confidence (may flag innocent users).
For residential proxy rows, see residential proxy detection best practices.

Formats

  • CSV - the schema above, gzipped plain text with one CIDR per row. Download sample.
  • MMDB - the same fields, packed into MaxMind's database format. Readable with any libmaxminddb-based library (Go, Python, PHP, Node, Java, .NET, and others). Download sample.
    Note: This MMDB is significantly larger than the standalone Proxy & VPN MMDB because it includes single-IP residential entries.

Samples are for format validation only. The data may be fictitious.

Delivery: enterprise direct download URL, refreshed hourly.

Interested?

Contact us

Built for enterprise and high-volume deployments.

Looking for real-time per-IP lookups instead? See our API.