Bot signals — AI crawler & agent

Amazonbot IP addresses

Amazonbot published crawling infrastructure, documented as supporting AI training among other uses; not proof every request trains AI.

risk.is_airisk.is_crawler Ranges Reviewed

Check an IP

Is this IP really Amazonbot?

Checks the address against what Amazonbot publishes, the same evidence behind risk.is_ai.

01 — Verification

How IPAPI.GR verifies Amazonbot.

Only from what Amazonbot publishes about itself. No third-party blocklists, no behavioural guesses. Live address counts change with every publication, so check the official file for the current list.

02 — In the response

What a match looks like.

A lookup of a Amazonbot address sets risk.is_ai and risk.is_crawler. The flags come with geolocation and network data in the same response, for Pro API keys.

This publication is AI crawling or retrieval traffic, so it counts as both an AI source and a crawler.

The response says which kind of bot an address belongs to, not which operator. Pair it with the user agent: a request that claims to be Amazonbot but doesn't match is unverified.

GET /api/lookup/{ip}?key=PRO_KEY
{
  // … location and network fields …
  "risk": {
    "is_ai": true,
    "is_crawler": true,
    "is_scanner": false
  }
}

03 — Questions

About Amazonbot.

Where does Amazonbot publish its IP addresses?

Amazonbot publishes its addresses at https://developer.amazon.com/amazonbot/ip-addresses/. IPAPI.GR reads that publication directly, not a third-party copy.

How often is the Amazonbot list refreshed?

IPAPI.GR re-fetches it every hour. If a refresh fails, the previous entries expire after at most 24 hours instead of being trusted forever.

Which risk flag does Amazonbot set?

A matching address sets risk.is_ai and risk.is_crawler in the lookup response. The risk flags are returned for Pro API keys.

Verify Amazonbot on every request.

Pro: 40,000,000 requests a day with is_ai, is_crawler and is_scanner in every lookup.