AI crawler access on .br domains
71 of the 376 domains measured in this segment refuse a request from an identified AI user agent at the edge, 19% of the segment, against 6% whose robots.txt disallows an answer engine at the site root. The block that costs these sites citations is not the one written in the file. That answer-engine rate is level with the corpus rate of 7%, which is itself measured across 30,225 domains.
Mean AI access score across those 376 domains is 75.6 of 100, 51 of them publish an llms.txt (14%), and 210 publish structured data an answer engine can parse (56%).
Block rate by crawler, inside this segment robots.txt at the site root
| Crawler | Operator | Content used for | Block rate | Blocking | Measured |
|---|---|---|---|---|---|
| GPTBot | OpenAI | training | 4.8% | 18 | 376 |
| CCBot | Common Crawl Foundation | archive | 4.5% | 17 | 376 |
| ClaudeBot | Anthropic | training | 4.3% | 16 | 376 |
| omgilibot | Webz.io | training | 3.7% | 14 | 376 |
| Google-Extended | training | 3.5% | 13 | 376 | |
| Bytespider | ByteDance | training | 3.5% | 13 | 376 |
| omgili | Webz.io | training | 3.2% | 12 | 376 |
| Diffbot | Diffbot | training | 3.2% | 12 | 376 |
| anthropic-ai | Anthropic | training | 3.2% | 12 | 376 |
| PerplexityBot | Perplexity | answer index | 2.9% | 11 | 376 |
| Amazonbot | Amazon | training | 2.9% | 11 | 376 |
| Meta-ExternalAgent | Meta | training | 2.7% | 10 | 376 |
| ChatGPT-User | OpenAI | live retrieval | 2.7% | 10 | 376 |
| AI2Bot | Allen Institute for AI | training | 2.7% | 10 | 376 |
| SemrushBot-OCOB | Semrush | training | 2.1% | 8 | 376 |
| cohere-ai | Cohere | live retrieval | 2.1% | 8 | 376 |
| Claude-User | Anthropic | live retrieval | 2.1% | 8 | 376 |
| YouBot | You.com | answer index | 1.9% | 7 | 376 |
| Perplexity-User | Perplexity | live retrieval | 1.9% | 7 | 376 |
| Scrapy | Zyte (open-source framework) | training | 1.6% | 6 | 376 |
| OAI-SearchBot | OpenAI | answer index | 1.6% | 6 | 376 |
| FacebookBot | Meta | training | 1.6% | 6 | 376 |
| DuckAssistBot | DuckDuckGo | live retrieval | 1.6% | 6 | 376 |
| cohere-training-data-crawler | Cohere | training | 1.6% | 6 | 376 |
| Applebot-Extended | Apple | training | 1.6% | 6 | 376 |
| Timpibot | Timpi | training | 1.3% | 5 | 376 |
| PanguBot | Huawei | training | 1.3% | 5 | 376 |
| Kangaroo Bot | Kangaroo LLM | training | 1.3% | 5 | 376 |
| ImagesiftBot | ImageSift (Hive) | training | 1.3% | 5 | 376 |
| MistralAI-User | Mistral AI | live retrieval | 1.1% | 4 | 376 |
| Meta-ExternalFetcher | Meta | live retrieval | 1.1% | 4 | 376 |
| Claude-SearchBot | Anthropic | answer index | 1.1% | 4 | 376 |
| Google-CloudVertexBot | live retrieval | 0.8% | 3 | 376 | |
| MistralAI-Training | Mistral AI | training | 0.5% | 2 | 376 |
| GoogleOther | training | 0.5% | 2 | 376 | |
| Bingbot | Microsoft | answer index | 0.5% | 2 | 376 |
| Applebot | Apple | answer index | 0.5% | 2 | 376 |
| msnbot | Microsoft | answer index | 0.3% | 1 | 376 |
| Meta-WebIndexer | Meta | answer index | 0.3% | 1 | 376 |
| facebookexternalhit | Meta | live retrieval | 0.3% | 1 | 376 |
| Amzn-User | Amazon | live retrieval | 0.3% | 1 | 376 |
| Amzn-SearchBot | Amazon | answer index | 0.3% | 1 | 376 |
| TikTokSpider | ByteDance | live retrieval | 0.0% | 0 | 376 |
| OAI-AdsBot | OpenAI | live retrieval | 0.0% | 0 | 376 |
| MistralAI-Index | Mistral AI | answer index | 0.0% | 0 | 376 |
| Meta-ExternalAds | Meta | training | 0.0% | 0 | 376 |
| Googlebot-News | answer index | 0.0% | 0 | 376 | |
| Googlebot | answer index | 0.0% | 0 | 376 |
Block rate is the share of this segment's domains holding a policy record for that agent whose robots.txt disallows it at the site root, shown with its numerator and denominator. Denominators differ between agents because a record only exists once a domain has been measured for it. A domain serving no robots.txt counts as allowing everything, which is what the standard specifies.
Most accessible
| Domain | Score | Engines blocked | llms.txt | |
|---|---|---|---|---|
| 1 | nivelguaiba.com.br | 100 | 0 | yes |
| 2 | bluesoft.com.br | 97 | 0 | yes |
| 3 | alura.com.br | 96 | 0 | yes |
| 4 | nuvemshop.com.br | 96 | 0 | yes |
| 5 | zapsign.com.br | 96 | 0 | yes |
| 6 | acordocerto.com.br | 96 | 0 | yes |
| 7 | meliuz.com.br | 96 | 0 | yes |
| 8 | xvideo.vlog.br | 96 | 0 | yes |
| 9 | bibliaonline.com.br | 96 | 0 | yes |
| 10 | sankhya.com.br | 95 | 0 | yes |
| 11 | forbes.com.br | 95 | 0 | yes |
| 12 | stone.com.br | 94 | 0 | yes |
| 13 | ton.com.br | 94 | 0 | yes |
| 14 | milvus.com.br | 94 | 0 | yes |
| 15 | tray.com.br | 94 | 0 | no |
Highest AI access scores among the 376 domains measured in this segment.
Least accessible
| Domain | Score | Engines blocked | llms.txt | |
|---|---|---|---|---|
| 1 | shopee.com.br | 29 | 0 | no |
| 2 | bb.com.br | 37 | 0 | no |
| 3 | itamaraty.gov.br | 38 | 0 | no |
| 4 | nelogica.com.br | 39 | 0 | no |
| 5 | registrocivil.org.br | 39 | 0 | no |
| 6 | amazon.com.br | 40 | 13 | no |
| 7 | mec.gov.br | 46 | 0 | no |
| 8 | jsuol.com.br | 46 | 0 | no |
| 9 | rdstation.com.br | 46 | 0 | no |
| 10 | clarowifi.com.br | 46 | 0 | no |
| 11 | autoglassonline.com.br | 46 | 0 | no |
| 12 | ipea.gov.br | 47 | 0 | no |
| 13 | b3.com.br | 47 | 0 | no |
| 14 | espn.com.br | 48 | 1 | no |
| 15 | acesso.gov.br | 49 | 0 | no |
Lowest AI access scores among the same 376 domains.
Compare with the rest of the grouping top-level domain segments
The largest 12 other segments in this grouping, ordered by size. The share beside each is that segment's own answer-engine block rate over its own count. Full table on the segments index.
What this segment does not tell you read this before citing it
A top-level domain is a weak proxy for jurisdiction. Most of them are open to any registrant anywhere, so a domain under a country-code registry may be operated from outside that country by a company no local law reaches. Read these rows as differences between registration communities and the publishing cultures inside them, not as differences between legal regimes.
Measure your own domain
The audit that produced every number on this page runs on any domain in about six seconds: robots.txt resolved for 48 agents, then live requests sent as four of them to see whether the edge agrees with the file.