VPN Proxy Detector API

GET

Spot visitors connecting through VPNs or datacenter servers.

VPN Proxy Detector checks any IP address to detect active VPN connections and cloud datacenter hosting. Lookups return boolean flags for VPN and datacenter status plus the verification date, with paid tiers adding Tor detection and risk levels.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/vpndetector?ip=103.62.49.210

Query parameters

ipstring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "ip": "103.62.49.210",
    "is_vpn": false,
    "is_datacenter": true,
    "is_tor": false,
    "asn": "AS137409",
    "asn_name": "GSLNETWORKS-AS-AP GSL Networks Pty LTD",
    "checked_on": "2026-09-14",
    "risk_level": "Moderate",
    "threat_level": "Low"
  }
}

About the VPN Proxy Detector API

A VPN detection API for any IPv4 or IPv6 address. It checks the IP against lists of commercial VPN exit ranges and cloud and hosting datacenter ranges, refreshed daily, and returns is_vpn and is_datacenter flags as JSON. There is no separate proxy flag: proxies hosted in a datacenter show up through is_datacenter, and residential proxies are not detected. Paid plans add Tor exit node status, the ASN and network name, and a risk and threat level derived from those flags.

What people use it for

Fraudulent Signup Prevention: To stop fake account spam, security platforms verify visitor IPs at registration to block traffic originating from known commercial VPNs and cloud servers.
Streaming Rights Compliance: Media providers check playback requests against datacenter and VPN flags to enforce territorial broadcasting rights on copyrighted video catalogs.
Payment Gateway Screening: When an online order is submitted, checkout systems check the buyer IP to trigger extra authentication steps if it belongs to a datacenter network.
Ad Click Validation: Advertising networks filter invalid traffic by screening incoming ad impressions for datacenter hosting IPs before recording billable user interactions.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use VPN Proxy Detector

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the VPN Proxy Detector API.

Read the docs →

Does it distinguish between consumer VPNs and cloud datacenter IPs?

Yes. The response separates whether an IP belongs to a commercial VPN service from whether it originates from a cloud provider or datacenter. This lets you enforce different policies for standard VPN users compared to automated hosting traffic.

Does it detect proxies as well as VPNs?

Only proxies running in a datacenter. The response has is_vpn and is_datacenter flags but no proxy flag, and most open and paid proxies sit on hosting networks, which is_datacenter catches. Residential proxies route through home ISP addresses and are not detected.

How far does the Starter plan go for IP lookups?

Starter provides 200,000 credits each month, covering 20,000 IP lookups at 10 credits per call. That works out to about $0.0015 per check or $1.50 per 1,000 lookups. The Free plan includes 20 checks every month for testing your integration.

Do I get Tor status and risk levels on the Free plan?

No. The Free plan returns whether an IP is a VPN or datacenter address, plus checked_on. Tor exit status, the ASN and network name, and the risk and threat levels require a paid subscription, starting with Starter.

How often is the VPN detection data updated?

The VPN and datacenter range lists are refreshed daily, and so is the Tor exit node list. Each response carries checked_on, the date the lookup ran against those lists.

Can I use this detection data in a commercial SaaS product?

Yes, provided you are on a paid plan. Commercial use is allowed across all paid tiers, including Starter. You can evaluate incoming traffic to protect signups or control access in your application, though redistributing or reselling the raw IP data is prohibited.

Request parameters — GET /v1/vpndetector

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`ip`Required	string	`103.62.49.210`	The IP address you want to check for VPN usage ip

Example request

1
2

curl "https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/vpndetector

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "ip": "103.62.49.210",
    "is_vpn": false,
    "is_datacenter": true,
    "is_tor": false,
    "asn": "AS137409",
    "asn_name": "GSLNETWORKS-AS-AP GSL Networks Pty LTD",
    "checked_on": "2026-09-14",
    "risk_level": "Moderate",
    "threat_level": "Low"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`ip`	string	`"103.62.49.210"`	The IP address that was checked for VPN usage
`is_vpn`	boolean	`false`	Whether the IP address is using a VPN service
`is_datacenter`	boolean	`true`	Whether the IP belongs to a datacenter or cloud provider
`is_tor`Premium	boolean	`false`	Whether the IP is a known Tor exit node; null if the Tor list could not be checked
`asn`Premium	string	`"AS137409"`	Autonomous System Number announcing the IP (e.g., AS16509); null if unrouted
`asn_name`Premium	string	`"GSLNETWORKS-AS-AP GSL Networks Pty LTD"`	Registered name of that AS (e.g., AMAZON-02), not always the company name
`checked_on`	string	`"2026-09-14"`	The date when the IP was last checked for VPN status
`risk_level`Premium	string	`"Moderate"`	Overall risk of the IP address: High for Tor exits and VPNs, Moderate for datacenter-only addresses, Low otherwise
`threat_level`Premium	string	`"Low"`	How strongly the IP anonymises its user: High for Tor exits, Moderate for VPNs, Low otherwise

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	VPN Proxy Detector calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/vpndetector

No SDK to install — this is a plain HTTPS call to /v1/vpndetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/vpndetector" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/vpndetector-apiSource, issues and the examples this page is built from.ReferenceVPN Proxy Detector API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/vpndetectornpm APIVerve.API.VPNProxyDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/vpndetector

Install the Node.js SDK, then call the VPN Proxy Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/vpndetector

Node.js

const res = await fetch("https://api.apiverve.com/v1/vpndetector", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/vpndetectorThe published Node.js client, versioned and signed.GitHubapiverve/vpndetector-apiSource, issues and the examples this page is built from.ReferenceVPN Proxy Detector API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.VPNProxyDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/vpndetector

No SDK to install — this is a plain HTTPS call to /v1/vpndetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/vpndetector",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/vpndetectornpm APIVerve.API.VPNProxyDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/vpndetector

Install the C# / .NET SDK, then call the VPN Proxy Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.VPNProxyDetector

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/vpndetector");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.VPNProxyDetectorThe published C# / .NET client, versioned and signed.GitHubapiverve/vpndetector-apiSource, issues and the examples this page is built from.ReferenceVPN Proxy Detector API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/vpndetectornpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/vpndetector

No SDK to install — this is a plain HTTPS call to /v1/vpndetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/vpndetector", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/vpndetectornpm APIVerve.API.VPNProxyDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/vpndetector

No SDK to install — this is a plain HTTPS call to /v1/vpndetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/vpndetector");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/vpndetectornpm APIVerve.API.VPNProxyDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/vpndetector

No SDK to install — this is a plain HTTPS call to /v1/vpndetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/vpndetector")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/vpndetectornpm APIVerve.API.VPNProxyDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

How to Detect VPN and Proxy UsersIdentify VPN, proxy, and datacenter IPs to prevent fraud and enforce geo-restrictions. Complete tutorial with code examples.Read

IP Geolocation: Accuracy, Limitations, and Best PracticesIP geolocation has limits. Learn when it works, when it fails, and how to handle edge cases in your applications.Read

IP Fraud Detection: VPNs, Tor, and BlacklistsBuild an IP-based fraud scoring system. Detect VPNs, Tor exit nodes, and blacklisted IPs before they cost you money.Read

VPN Proxy Detector API

Try it — live request, no key required

About the VPN Proxy Detector API

What people use it for

Ways to call it

Other ways to use VPN Proxy Detector

Questions.

Request parameters — GET /v1/vpndetector

Required

Authentication

Response — GET /v1/vpndetector

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — GET /v1/vpndetector

Resources

Also published for

Call it from Node.js — GET /v1/vpndetector

Resources

Also published for

Call it from Python — GET /v1/vpndetector

Resources

Also published for

Call it from C# / .NET — GET /v1/vpndetector

Resources

Also published for

Call it from Go — GET /v1/vpndetector

Resources

Also published for

Call it from PHP — GET /v1/vpndetector

Resources

Also published for

Call it from Ruby — GET /v1/vpndetector

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — VPN Proxy Detector API

Networking

Related articles

Ready to build with VPN Proxy Detector? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog