VPN Server IP List by Provider
Pick a VPN provider to see every server IP it publishes, search the list, download it for blocklists or log correlation, and open any server address to see its hosting network and location.
🔒 The list is downloaded from the public, CC0-licensed source directly to your browser; IGRS does not log what you view or download.
Where these server lists come from
VPN companies publish the addresses of their servers so their own apps and configuration files can connect to them — through public server-list APIs, downloadable configuration bundles or relay directories. The open-source-vpn-ip-lists project collects that first-party data every day for ten providers and releases it into the public domain under CC0. Nothing here comes from guesswork, traffic scraping or commercial GeoIP databases: if an address is listed, the provider itself published it as one of its servers.
| Provider | Coverage |
|---|---|
| NordVPN | The largest list, several thousand IPv4 server addresses |
| Private Internet Access, Proton VPN, Windscribe | Around one to two thousand addresses each |
| Mullvad, AirVPN | IPv4 and IPv6 addresses |
| Surfshark, IVPN, OVPN, RiseupVPN | Smaller published fleets |
Exact counts are shown above when you open a list, because fleets grow and shrink daily.
VPN IP to server: identifying the server behind an address
Clicking any address opens the IGRS IP lookup for that server. It shows the hosting company and ASN that actually run the machine (VPN providers rent capacity from datacenter operators), the routed prefix, the reverse-DNS name the operator assigned — which for some providers encodes the server's city and number — and the approximate location. Together with the provider name, this tells you which VPN brand, which hosting network and which region a suspect's traffic passed through.
Practical uses
- Log correlation: download a provider's list and search your web, VPN-gateway or authentication logs for it to measure how much traffic comes through that service.
- Fraud and account-takeover triage: logins from a VPN server combined with a new device or a password reset are a classic takeover pattern worth a step-up check.
- Policy enforcement: organisations that do not allow consumer VPNs on corporate networks can use the lists to spot connections to them.
- Investigations: when platform records show a VPN address, the provider name tells you the trail continues with the VPN company or with non-IP evidence — not with an Indian telecom operator.
Blocking every VPN address will also block legitimate users who rely on VPNs for privacy and security. Treat a VPN match as one risk signal among several. Use of a VPN is lawful in India; providers operating here are subject to CERT-In's 2022 directions on keeping subscriber records.
Open data sources (all free, keyless)
| Data | Source | Terms |
|---|---|---|
| ASN, routed prefix, WHOIS, abuse contact, RIR | RIPEstat Data API — RIPE NCC | Free public API; IGRS identifies itself with sourceapp=igrs-xyz |
| Approximate location (city/region/timezone) | GeoJS (open-source project) and MaxMind GeoLite2 via RIPEstat | Free, no key |
| Reverse DNS, domain → IP | Cloudflare DNS-over-HTTPS | Free public resolver |
| Tor relays and exit nodes | Tor Project Onionoo | Free public API |
| VPN server IPs (NordVPN, Proton VPN, Mullvad, PIA, Surfshark, Windscribe, AirVPN, IVPN, OVPN, RiseupVPN) | open-source-vpn-ip-lists, built from data each provider publishes itself, refreshed daily | CC0 public domain |
The engine, iplookup.js, is plain JavaScript released under the MIT licence — read it, audit it, or reuse it in your own OSINT tooling. If you maintain an open dataset that would improve these checks, tell us and we will credit it here.
Frequently Asked Questions
For lawful investigation, security operations, research and awareness. Public network data describes networks, not people; confirm findings through official process before any action.