CrawlCheck

Agent view · Findings · 2026-11-13

Claude-User uses two published address lists. We checked one

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/claude-user-comes-from-two-published-address-lists-we-checked-one: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.

status200
content-typetext/markdown; charset=utf-8
varyAccept
link<https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/blog/claude-user-comes-from-two-published-address-lists-we-checked-one>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes11,354
words1,476
sha-256f31ec149493c8205620e20925fa24761e345c2c20d0c65b00421ad0c284a4bed
repr-digestsha-256=:8x7BSUk8ggViDiCSX6JHYeNFwsINDGWwBCGtDChKS+0=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795180557;expires=1795184157;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="M6PcztmnYb6cIVTm8jwRqA";tag="crawlcheck-page"
signaturesig1=:xME+w9lYMFvcI6nJl2DN1FVK/mL+7e+wbuMRjIjwQciB2zHnvMKQc8TvJb0kXSMTJvrIvYf4Tk6oVr2cwB1aBA==:
verifiedyes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3599 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba
Findings · 2026-11-13 · By [VSNARY | Emmanuel Orta](/author) · 1 view

# Claude-User uses two published address lists. We checked one

Anthropic publishes a crawler address list and a separate list of outbound addresses. Claude-User can arrive from either. We compared against the first only, and filed real requests as failed.

Until 13 November 2026 CrawlCheck checked requests named Claude-User against one list only, Anthropic's crawler file. Anthropic also publishes outbound address ranges, 160.79.104.0/21 and 153.61.208.0/20, and Claude-User fetches arrive from those too. Requests from the second list were counted as failing verification. The check now accepts both lists for Claude-User. 602 earlier rows remain filed as failed and have not been reclassified.

On this page

- The two lists
- How we found it
- What changed
- What is still wrong
- If you check crawlers yourself

Two published lists, one checked

Crawler addresses for ClaudeBot, Claude-SearchBot and Claude-User

Published as

A JSON file on claude.com

We checked it

Yes

Outbound address ranges: 160.79.104.0/21 and 153.61.208.0/20

Published as

A page in Anthropic’s API documentation

We checked it

No, until 13 November 2026

Claude-User is the fetcher Anthropic uses when a person asks Claude to open a page. We verify a crawler by comparing the request's address with what its operator publishes. For Claude-User we compared against one list when there are two.

## The two lists #

| List | Published as | We checked it |
| --- | --- | --- |
| Crawler addresses for ClaudeBot, Claude-SearchBot and Claude-User | A JSON file on claude.com | Yes |
| Outbound address ranges: 160.79.104.0/21 and 153.61.208.0/20 | A page in Anthropic's API documentation | No, until 13 November 2026 |

## How we found it #

We asked Claude to fetch pages on this site and watched the requests arrive. They carried the Claude-User name and came from 160.79.106.14 and 153.61.208.9. Both addresses sit inside the outbound ranges Anthropic publishes. Our record marked them as failing verification.

## What changed #

Claude-User is now accepted from either list. The change is narrow on purpose: a request named ClaudeBot from the outbound ranges still fails, because Anthropic lists ClaudeBot's addresses in the crawler file only. An address outside both lists still fails, and so does an address Anthropic has retired.

## What is still wrong #

Before the fix, 602 requests named Claude-User were filed as failing. Some of those were real. We have not gone back and reclassified them, so the historical failed count for Claude-User is too high. We have also not yet confirmed the fix against a visit we did not trigger ourselves.

## If you check crawlers yourself #

The lesson is general: an operator can publish more than one list, and on-demand fetchers are the likeliest to use a different one from the index crawler. Before you block a fetcher for failing an address check, look for a second list in the operator's documentation. Our [mirror of operator lists](/ai-crawlers/ip-ranges.json) covers the crawler files; it does not replace reading the operator's pages.

And remember that [what each operator says about robots.txt](/guides/robots-txt-does-not-stop-user-triggered-ai-fetchers) differs for this kind of fetcher too. Anthropic says Claude-User follows it.

CrawlCheck’s dataset when this page loaded: 570,959 sites measured.

Written by

[Emmanuel Orta](/author) · VSNARY

I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.

[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)

Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fclaude-user-comes-from-two-published-address-lists-we-checked-one%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fclaude-user-comes-from-two-published-address-lists-we-checked-one%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Claude-User%20uses%20two%20published%20address%20lists.%20We%20checked%20one)[Email](mailto:?subject=Claude-User%20uses%20two%20published%20address%20lists.%20We%20checked%20one&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fclaude-user-comes-from-two-published-address-lists-we-checked-one)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### What IP addresses does Claude-User come from?

Anthropic publishes a crawler address file on claude.com and, separately, outbound ranges 160.79.104.0/21 and 153.61.208.0/20 in its API documentation. Claude-User requests can arrive from either.

### Why did CrawlCheck mark real Claude-User requests as failed?

It compared them with the crawler file only. Requests from the outbound ranges were not on that list, so they were counted as failing verification until 13 November 2026.

### Does ClaudeBot use the outbound ranges too?

We do not accept it from them. Anthropic lists ClaudeBot's addresses in its crawler file, so a ClaudeBot request from the outbound ranges still fails our check.

### Were the old Claude-User counts corrected?

No. 602 earlier requests remain filed as failed. Some were real, so the historical failed count for Claude-User is overstated.

## Related findings

[2026-10-03 Verify GPTBot, ClaudeBot and PerplexityBot: tools compared How to verify GPTBot, ClaudeBot and PerplexityBot requests: published IP lists, CrawlCheck's free log check and Cloudflare verifie](/guides/how-to-verify-gptbot-claudebot-and-perplexitybot-tools-compared)[2026-11-13 Our mirror relayed real crawlers and inflated forgery counts A mirror we ran relayed Meta and Amazon crawler requests to crawlcheck.io, and we counted them as failed checks. Closed 13 Novembe](/blog/our-mirror-relayed-real-crawlers-and-inflated-our-forgery-counts)[2026-11-13 AI crawler IP ranges from 18 operator lists, in one file One JSON file mirrors 18 operator-published crawler address lists, refreshed hourly, with a checksum and status per source.](/blog/ai-crawler-ip-ranges-from-18-operator-lists-in-one-file)

The main product

Found this on your own site? **We fix it for $100.**

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)

Free browser extension

Check this on any site you open, **without leaving the page.**

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)

Write for the library

Measured something yourself? **Submit an article.**

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week

Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).

## Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.

Send for review

Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.

[All findings](/blog) · [The dataset](/data) · [How the dataset works](/policy)

We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)

#### How we measure, and our own machine files

CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).

**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.

**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.

**Pages:** [Keys](/keys) · [/](/) · [Listing check](/listing-check) · [SDK](/sdk) · [Site](/video/site) | **Datasets:** [Mississippi](/datasets/state/mississippi) · [Technologies: Bootstrap](/datasets/technologies/bootstrap) · [Problems: Robots ctype](/datasets/problems/robots-ctype) | **AI crawlers:** [Klaviyoaibot](/ai-crawlers/klaviyoaibot) | **Glossary:** [AI classifiers: Digital presence signals](/glossary/ai-classifiers/digital-presence-signals) · [security.txt](/glossary/security-txt) · [CDN](/glossary/cdn)

[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)

Same body as a file: /blog/claude-user-comes-from-two-published-address-lists-we-checked-one.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.