AI crawler policy › domain suffix

AI crawler blocking on .space sites

Latest sealed date 2026-08-07.

The panel contains 97 .space domains. On 2026-08-07, 37 of them served a robots.txt we could parse; 43 could not be reached at all and have no observed policy. Of the parsed ones, 11 (29.7%) name at least one tracked AI crawler and 11 (29.7%) block at least one site-wide. 3 block every crawler via the wildcard group, counted separately.

In the latest sealed reading for .space on 2026-08-07, 8 tracked crawler tokens were named by at least one observed file: Amazonbot: 11 named, 11 blocked site-wide; Applebot-Extended: 11 named, 11 blocked site-wide; Bytespider: 11 named, 11 blocked site-wide; CCBot: 11 named, 11 blocked site-wide; ClaudeBot: 11 named, 11 blocked site-wide; Google-Extended: 11 named, 11 blocked site-wide; GPTBot: 11 named, 11 blocked site-wide; meta-externalagent: 11 named, 11 blocked site-wide. Each entry keeps the named count before the fully-blocked count. A tracked token absent from the list had zero observed mentions; the counts describe file declarations, not crawler behavior.

What "suffix" means here. The final DNS label, not the effective top-level domain. A .co.uk site is counted under .uk. Computing a true effective TLD needs the Public Suffix List, which this surface does not ship, and approximating one would put a wrong denominator under every figure on this page.

Every tracked crawler on .space

CrawlerOperatorNames itBlocks outright% of parsed
AmazonbotAmazon111129.7%
Applebot-ExtendedApple111129.7%
BytespiderByteDance111129.7%
CCBotCommon Crawl111129.7%
ClaudeBotAnthropic111129.7%
Google-ExtendedGoogle111129.7%
GPTBotOpenAI111129.7%
meta-externalagentMeta111129.7%

Blocks outright — the file has a group for that exact product token containing Disallow: / with no overriding allow. Partly restricts — a group exists with at least one non-empty Disallow, but not the whole site. Names & allows — a group exists with no effective Disallow. Everything else is not mentioned: the wildcard * group governs it, and wildcard effects are counted separately rather than folded in, because a site that blocks everything has not made a decision about any AI crawler in particular. Matching is exact and case-insensitive per RFC 9309 — never substring.

Get told when .space change their AI crawler rules

Sites publish today's robots.txt and overwrite it — no archive, no history, no notification. We keep a dated daily copy. Leave your email and we'll send you what moved for .space: who started blocking, who stopped, and on which day.

Email me changes for .space →

Work email only. No newsletter, no obligation.

Prefer to just buy it? See the sealed-archive monitoring offers, priced, with a dated sample.

14 newest sealed readings for .space

For each date, the table keeps the panel count beside the parseable robots.txt denominator, the sites naming or blocking a tracked AI crawler, and wildcard blocks. Unreachable or unusable responses are excluded rather than treated as permissive. These are aggregate observations of published files, not crawler behavior or the intent behind a declaration.

Across the 14 sealed readings shown for .space, the newest recorded 37 domains publishing a parseable robots.txt, against an observed low of 37 on 2026-08-07 and a high of 39 on 2026-08-06. In the newest reading, 11 named at least one tracked AI crawler (range 11 on 2026-08-01 to 12 on 2026-07-31), while 11 blocked at least one (range 11 on 2026-08-01 to 12 on 2026-07-31). These are aggregate observations of published files. A movement can reflect changed fetch coverage as well as a changed file; it does not describe motive or crawler behavior.

Sealed datePanel domainsParsedNames anyBlocks anyWildcard block
2026-08-07973711113
2026-08-06973911114
2026-08-05973911114
2026-08-04973911114
2026-08-03973911114
2026-08-02973911114
2026-08-01973911114
2026-07-31973912124
2026-07-30973812123
2026-07-29973912124
2026-07-28973912124
2026-07-27973912124
2026-07-26973812124
2026-07-25973912124
Read this before quoting a trend. We hold 55 sealed daily snapshots between 2026-06-09 and 2026-08-07, out of 60 calendar days. 5 calendar day(s) inside that span have no collection run at all: 2026-06-11, 2026-06-12, 2026-06-19, 2026-07-04, 2026-07-15. Consecutive rows in every table below are consecutive SEALED dates, not consecutive days — where a gap falls, that row's diff covers more than 24 hours, and the span is printed with it. We do not interpolate across a day we did not collect.

Observed AI-crawler verdict changes on .space

Across the sealed archive, 8 crawler-verdict transitions were attributed to .space domains on 1 sealed change dates. The newest aggregate movements are listed below; no domain name or fetched file body is published.

Sealed dateCrawlerVerdict movedDomains
2026-08-01Amazonbotblocked outright → not mentioned1
2026-08-01Applebot-Extendedblocked outright → not mentioned1
2026-08-01Bytespiderblocked outright → not mentioned1
2026-08-01CCBotblocked outright → not mentioned1
2026-08-01ClaudeBotblocked outright → not mentioned1
2026-08-01Google-Extendedblocked outright → not mentioned1
2026-08-01GPTBotblocked outright → not mentioned1
2026-08-01meta-externalagentblocked outright → not mentioned1

Compiled from each site's own published /robots.txt, /ai.txt, /llms.txt and /.well-known/tdmrep.json, fetched daily over a frozen 100,000-domain research panel (source list: Tranco; no Tranco rank is republished here). Verdicts are mechanical readings of what those files say under RFC 9309 grouping with exact product-token matching — they are not legal advice, not a statement about any site's intentions, and not a claim about what any crawler actually did. A robots.txt is a request, not an access control. Figures are provided for informational purposes only and carry no warranty of accuracy or completeness.

AI crawler policy home · What changed · How this is collected · US Tech Automations.