AI training crawler · Amazon

Amazonbot user agent, IP ranges and robots.txt

Amazonbot is Amazon's AI training crawler. It identifies itself with the Amazonbot user-agent token, honors robots.txt according to its operator, and runs from 525 published IP prefixes.

Operator
Amazon
Reviewed
September 2026
Sources
2
Operator
Amazon
User-agent token
Amazonbot
Purpose
AI training crawler
robots.txt token
Amazonbot
Honors robots.txt
Yes, per the operator
Published IP ranges
Yes, 525 prefixes (525 IPv4, 0 IPv6)
Verification
Amazon publishes an IP address list for Amazonbot at https://developer.amazon.com/amazonbot/ip-addresses/, linked from the documentation as 'Published IP Addresses' and embedded as JSON within an HTML page rather than served as a raw JSON endpoint. Entries are single IPv4 addresses without a CIDR suffix; no IPv6 entries are listed. No reverse DNS suffix is documented.
Full user-agent example
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amazonbot/0.1) Chrome/W.X.Y.Z Safari/537.36

Block or allow Amazonbot in robots.txt

Use the token Amazonbot in robots.txt. Amazon documents that Amazonbot honors robots.txt directives.
Block everything
User-agent: Amazonbot
Disallow: /
Allow everything
User-agent: Amazonbot
Allow: /

Verify a request is really Amazonbot

Anyone can put Amazonbot in a User-Agent header. Amazon publishes an IP address list for Amazonbot at https://developer.amazon.com/amazonbot/ip-addresses/, linked from the documentation as 'Published IP Addresses' and embedded as JSON within an HTML page rather than served as a raw JSON endpoint. Entries are single IPv4 addresses without a CIDR suffix; no IPv6 entries are listed. No reverse DNS suffix is documented.

Published IP ranges

Amazon lists addresses on its documentation page rather than in a machine-readable file. Our probe read that page on 2026-09-06 and extracted the entries below.

Prefixes
525
IPv4
525
IPv6
0

First entries at fetch time: 84.15.177.17, 3.81.253.213, 3.89.170.186

SHA-256 of the fetched body: ef2a1fdd9146c9d02f3fbd488736fcb12789cc58932e89245bc0781613910899

Open the source page

What Amazonbot does

Amazon operates Amazonbot, which its documentation says is used to improve Amazon products and services, to give customers more accurate information, and may be used to train Amazon AI models. It honors robots.txt under the token Amazonbot. Site owners verify it against Amazon's published IP address list; Amazon does not document a reverse DNS suffix.

In access logs the crawler identifies itself with the token Amazonbot inside a browser-like user agent string, for example "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amazonbot/0.1) Chrome/W.X.Y.Z Safari/537.36". Amazon describes the visits as a way to improve its products and services, which it says helps it provide more accurate information to customers, and the fetched content may be used to train Amazon AI models. This registry classes it as AI training for that reason. Amazon does not document whether the crawler executes JavaScript.

Allowing Amazonbot lets Amazon fetch your pages for those uses, including possible model training. Blocking it with a Disallow rule for the Amazonbot token stops those fetches. Amazon also says that sites which allow Amazonbot in robots.txt may be eligible for the Amazon Content Partners program at contentpartners.amazon.com. If you want a page fetched but not used for model training, Amazon says it respects a page-level meta robots noarchive tag, which it reads as "do not use the page for model training". It also honors noindex and none at page level and rel=nofollow at link level.

Amazon's documentation spells out its robots.txt handling. The crawler fetches robots.txt per host, so site.example.com/robots.txt is read separately from example.com/robots.txt, and it may use a cached copy from the last 30 days. If robots.txt cannot be fetched, the crawler behaves as if the file does not exist. It does not support the crawl-delay directive, and Amazon says settings changes can take around 24 hours to take effect. Questions go to amazonbot@amazon.com.

Operator note. Amazon's documentation states that Amazonbot respects the Robots Exclusion Protocol, honoring user-agent and allow/disallow directives; it fetches the host-level robots.txt or uses a cached copy from the last 30 days, checks robots.txt per host (for example site.example.com/robots.txt separately), and behaves as if robots.txt does not exist when it cannot be fetched. It respects link-level rel=nofollow and the page-level meta robots directives noarchive ('do not use the page for model training'), noindex and none, does not support the crawl-delay directive, and settings changes may take about 24 hours to take effect. The contact address is amazonbot@amazon.com, and the documentation says sites allowing Amazonbot in robots.txt may be eligible for the Amazon Content Partners program (contentpartners.amazon.com). JavaScript execution is not documented.

Common questions

Should I block Amazonbot?
That depends on whether you want Amazon to use your content. Amazon says fetched pages may train Amazon AI models, so blocking removes that use. Amazon also says sites that allow the crawler may be eligible for its Content Partners program. A middle option is meta robots noarchive, which Amazon reads as a request not to use the page for model training.
How do I verify Amazonbot?
Compare the requesting IP with Amazon's published list at developer.amazon.com/amazonbot/ip-addresses/. It is an HTML page with a JSON blob in a code block, not a raw JSON endpoint. The blob has a prefixes array of ipv4Prefix values. Amazon does not document a reverse DNS suffix, so IP matching is the only documented check.
Does Amazonbot run JavaScript?
Amazon's documentation does not say. The user agent string includes Chrome and Safari tokens, but that does not confirm rendering. Treat JavaScript execution as undocumented and check your own logs for asset requests if you need to know.

Sources

The operator documentation used for this entry. Recorded review date September 2026; consult the linked pages for current policy and compare them with this dated snapshot.

  1. [1]https://developer.amazon.com/amazonbot
  2. [2]https://developer.amazon.com/amazonbot/ip-addresses/

This registry documents how operators describe their own bots so site owners can identify and control them. It does not publish third-party IP lists or guess at undocumented behaviour. To see how your own site responds to automated visitors, the bot detection scanner reads a URL's live response and names the protection it finds.