VPN IP Extended
VPN IP v1 with evidence data behind every range.
| ID | vpn_ip_extended_v1 |
|---|---|
| Formats | csvgz, mmdb |
| Update Frequency | Daily |
| Last Updated | November 16th 2026 (yesterday) |
| Entries | 15,497,076 |
File Size (csvgz) | 111 MB |
File Size (mmdb) | 139 MB |
Overview
Everything in VPN IP, plus a method column recording how each range was established. Use it when a single confidence grade is too coarse and you want to weight ranges by the kind of evidence behind them.
Formats
curl -L -o vpn_ip_extended_v1.csv.gz -X GET "https://internetdata.io/api/v2/database/download?id=vpn_ip_extended_v1&format=csvgz&apikey=$APIKEY"| Name | Type | Description |
|---|---|---|
start_ip | ipaddress | Start IP of the IP range. |
end_ip | ipaddress | End IP of the IP range. |
provider | string | Commercial VPN provider's unique ID. Empty when the range is confirmed VPN infrastructure we have not yet attributed to a named operator. |
method | string | How this range was established. Values are listed below.
|
confidence | string | Confidence of the correctness of this observation. |
last_seen | date | Last time this observation was made. |
| start_ip | end_ip | provider | method | confidence | last_seen |
|---|---|---|---|---|---|
122.228.200.155 | 122.228.200.155 | softether_org | scan | low | 2026-11-13 |
159.112.211.50 | 159.112.211.50 | watchguard | scan | low | 2026-11-14 |
2001:ac8:23:500:1011:df6b:26e1:e9d4 | 2001:ac8:23:500:1011:df74:2db2:321f | ovpn | infer | high | 2026-11-16 |
5.133.21.101 | 5.133.21.101 | draytek | scan | low | 2026-11-13 |
108.198.110.133 | 108.198.110.133 | watchguard | scan | low | 2026-11-08 |
Method
method is a small, stable vocabulary. New methods are folded into an existing class, so you can switch on these values and stay correct as our coverage grows.
scan
We spoke the VPN's protocol ourselves and got a valid server response. It's a direct observation that the address runs VPN server software.
Where provider is empty, the address is confirmed VPN infrastructure that we were unable to tie to a named provider at the current time. It may be attributed later, or it may be non-commercial, or simply a corporate VPN setup.
scrape
The provider published the address publicly or privately, either through its own API, client software, configuration, DNS, or website, and we were able to query it or reverse engineer it.
registry
Public registration and naming records attribute the range to the provider, including RIR WHOIS netname and organization fields, reverse-DNS naming, and self-published geofeeds.
infer
The address sits inside a small prefix in which we independently confirmed a large threshold of VPN addresses. This extends coverage across the remainder of a block a provider is demonstrably operating from.
Confidence vs. Method
method says what kind of evidence placed a range, and confidence how far that evidence holds for this provider, so one method can carry different grades for two providers. infer can be nearly always right for a provider that leases whole /24s, and high, while for another it's a guess from a threshold being reached, and low. registry from reverse DNS is high for a provider whose names are kept current and forward-confirmed, and lower for one whose names go stale.