VPNDetectionVPNDetection

Lookup your own address

GET
/myip

Answers what is known about the address this request came from, which is the same answer GET /{ip} gives for that address: the plan behind the presented key decides which fields come back, and the request counts against the same allowance.

The address is the one our edge observed, so a request through a proxy or a VPN reports the exit it left through rather than the machine that made it. That is usually the point of asking.

Authorization

apikey<token>

?apikey=<key>. Convenient in a browser; prefer a header elsewhere.

In: query

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://api.vpndetection.io/myip"
{
  "ip": "45.83.91.1",
  "is_vpn": true
}

{
  "error": "invalid API key"
}

{
  "error": "source address not allowed for this API key"
}

{
  "error": "rate limit exceeded"
}

{
  "error": "lookup failed"
}

Lookup GET

Answers what is known about a single IPv4 or IPv6 address. Which fields come back is decided by the plan behind the presented key; with no key the answer is `ip` and `is_vpn`.

List GET

Every database this organization may SEE, with where its licence stands. Not just the ones you hold: a customer with one grant should be able to tell what else is published without asking. `standing` is the difference - `licensed`, `expired`, or `unlicensed` for one never bought.