The VPN dataset identifies IP ranges used as exit points by VPN providers, covering large commercial services as well as self-hosted endpoints on cloud infrastructure.
Combined with the Proxy, Tor and Relay datasets it gives a complete picture of anonymized traffic reaching your platform.
The data
Inside the file
One record per row, a commented header line first. This is what ipregistry-vpn.csv looks like:
# ip_start,ip_end194.90.115.199,194.90.115.19946.165.182.30,46.165.182.30155.138.164.4,155.138.164.491.89.0.231,91.89.0.23183.132.21.36,83.132.21.36The rows above come from the free sample. Every build ships with MD5, SHA-1, SHA-256 and SHA-512 checksums so you can verify downloads.
| Column | Description |
|---|---|
ip_start | First IP address of the range, IPv4 or IPv6. |
ip_end | Last IP address of the range, inclusive. |
The MMDB variant carries the same data in a memory-mapped binary tree, compatible with the standard MMDB reader libraries available for every major programming language.
Downloads
Available formats
| Format | Description | Size |
|---|---|---|
| CSV | Plain text, one range per line. Import into any database or data warehouse. | 112 MB |
| CSV (zipped) | Same file compressed for faster downloads and cheaper storage. | 23.8 MB |
| MMDB | Binary format for instant lookups with standard MMDB readers. | 119 MB |
Use cases
What you can build
- Detect location spoofing in streaming, gaming and gambling
- Apply step-up verification for anonymized signups
- Separate privacy-conscious users from abuse in risk models
- Enforce regional pricing and licensing agreements
Related use cases: Cyber security · Compliance
Datasets are available with an Ipregistry subscription and download from your dashboard, or over a stable URL for automated syncs. Prefer live data? The same intelligence is served by the Ipregistry API.