AI crawler policy › domain suffix

AI crawler blocking on .to sites

Latest sealed date 2026-08-07.

In the latest sealed reading for .to on 2026-08-07, 26 tracked crawler tokens were named by at least one observed file: CCBot: 38 named, 37 blocked site-wide; Amazonbot: 37 named, 37 blocked site-wide; Applebot-Extended: 37 named, 37 blocked site-wide; Bytespider: 37 named, 37 blocked site-wide; ClaudeBot: 37 named, 37 blocked site-wide; Google-Extended: 37 named, 37 blocked site-wide; GPTBot: 37 named, 37 blocked site-wide; meta-externalagent: 37 named, 37 blocked site-wide; ImagesiftBot: 2 named, 2 blocked site-wide; AI2Bot: 1 named, 1 blocked site-wide; ChatGPT-User: 1 named, 1 blocked site-wide; Claude-SearchBot: 1 named, 1 blocked site-wide; Claude-User: 1 named, 1 blocked site-wide; cohere-ai: 1 named, 1 blocked site-wide; cohere-training-data-crawler: 1 named, 1 blocked site-wide; Diffbot: 1 named, 1 blocked site-wide; DuckAssistBot: 1 named, 1 blocked site-wide; FacebookBot: 1 named, 1 blocked site-wide; Google-CloudVertexBot: 1 named, 1 blocked site-wide; meta-externalfetcher: 1 named, 1 blocked site-wide; OAI-SearchBot: 1 named, 1 blocked site-wide; omgili: 1 named, 1 blocked site-wide; omgilibot: 1 named, 1 blocked site-wide; PanguBot: 1 named, 1 blocked site-wide; PerplexityBot: 1 named, 1 blocked site-wide; Timpibot: 1 named, 1 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.

Every tracked crawler on .to

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.

14 newest sealed readings for .to

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 .to, the newest recorded 137 domains publishing a parseable robots.txt, against an observed low of 134 on 2026-08-01 and a high of 140 on 2026-07-27. In the newest reading, 39 named at least one tracked AI crawler (range 35 on 2026-07-25 to 39 on 2026-08-07), while 38 blocked at least one (range 34 on 2026-07-25 to 38 on 2026-08-07). 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.

Observed AI-crawler verdict changes on .to

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