Skip to content
VPNDetection

Changelog

Changes to the VPNDetection API, its answers and its documentation that affect your integration, newest first, each with its date.

This page records each change to the API, its answers and these docs that can affect your integration. Each official library, the CLI and the MCP server keep their own release notes on GitHub, linked from their integration pages.

2026-11-21

  • Every answer now includes is_bot, which says whether a crawler, monitor, scanner or other bot uses the address. A paid plan's answer adds the bot object, which names the bot's operator, the bots it runs, what they do and whether the operator vouches for the address. See IP lookup.
  • On a paid plan, a lookup can send the User-Agent of the request you're deciding on as user_agent, and a batch can send each address's in user_agents. The answer's user_agent then names the agent and says whether the address bears it out.
  • Bot IP and its operator catalog, Bot Provider, are new databases.

2026-11-20

  • These docs now include Get started, Guides and Resources, with a migration guide for each provider you might move from. When you're signed in, code samples show your own key, masked, and copying a sample fills it in after you confirm it's you.
  • The free plan's answer now includes is_anycast, the reverse DNS hostname, and the country and rpki_status of the network that announces the address. See IP lookup.
  • The OpenAPI spec types satellite.asn as a 64-bit integer, as asn.asn already is, so a generated client reads an AS number of any size. Each IAM API endpoint now names the scope it needs in its description, since OpenAPI lists scopes only for OAuth schemes.

2026-11-19

  • A 429 for a burst of lookups past your organization's overage cap now tells you to raise the cap in Billing. See Rate limits.
  • A paid plan's answer now says whether the address belongs to a mobile carrier or a satellite operator, which services answer on it (SSH, SMTP, web, DNS resolver and BitTorrent), its city, the company that uses it and its abuse contact.

2026-11-17

  • When a paid key passes its organization's overage cap, lookups now answer 200 with the free plan's fields and cap_reached: true, instead of an error.

2026-11-16

  • Every lookup endpoint refuses a key that lacks the ip.lookup scope with 403. See Authentication.

2026-11-14

  • Every answer includes is_bogon, and each provider's display name (provider_name) next to its ID.

2026-11-11

  • The free plan has no daily or monthly cap, with or without a key, and a free account can try every field.
  • A batch of more than one address with a free-plan key is refused with 402. See Batch.

2026-11-05

  • A key sent over plain HTTP is refused. Send keys over HTTPS only.

2026-10-20

  • Every paid plan answers every field. Paid plans differ only in how many lookups they include.

2026-10-18

  • A paid plan's answer flags public proxies with is_pubproxy, with details in pubproxy.

2026-10-17