atp.fox
No parsable robots.txt — the URL did not respond.
How this site compares
Each row is one measured trait, not a composite score. Rank peers are Ranks 10,001–100,000; the second comparison is the full observed Tranco panel. Populations differ by metric and are printed with every rate.
| Trait | This site | Ranks 10,001–100,000 | Observed Tranco panel |
|---|---|---|---|
| robots.txt served | Fetch failed: dns_error | 59.7% of 91,507 | 61.7% of 1,212,578 |
| robots.txt returned 404 | Fetch failed: dns_error | 7.9% of 91,507 | 8.4% of 1,212,578 |
| Blanket disallow | Parsing unavailable | 4.0% of 54,147 | 10.3% of 740,113 |
| Effectively open file | Parsing unavailable | 22.6% of 54,147 | 25.7% of 740,113 |
| Wildcard group | Parsing unavailable | 92.1% of 54,147 | 89.8% of 740,113 |
| Sitemap declared | Parsing unavailable | 61.7% of 54,147 | 60.7% of 740,113 |
| Over the RFC parse limit | Parsing unavailable | 0.2% of 54,147 | 0.3% of 740,113 |
How these comparisons are measured
Status rates use canonical robots.txt observations. File traits use only parsed canonical files. A missing metric stays unavailable rather than becoming 0%. Rank bands are exclusive, so Ranks 10,001–100,000 does not include more popular bands.
Treatment by purpose
Declared purpose comes from the versioned agent registry. These are separate policy dimensions, not inputs to a score. An unnamed purpose is not automatically allowed; it inherits the wildcard rule described below.
Named agents
File evidence
robots.txt details
Crawl posture history
Google's interpretation of this robots.txt over status history (§3.3).
Compare atp.fox
Put this site's measured policy beside another site. Botfy keeps missing evidence visible and does not assign a score or winner.
Live files on atp.fox
The file as it exists on the host right now — may differ from what we measured. We link out rather than mirror (we store derived metrics, not raw bodies).
/robots.txt ↗ /llms.txt ↗ /llms-full.txt ↗ /ai.txt ↗
Raw observations
2 crawls, every source
A domain usually has more than one observation per crawl because we see it in the Common Crawl shard stream and fetch it ourselves. These are not duplicates — they are independent observations of the same file, and one is marked canonical. The rest of this page reads the canonical row.
CC-MAIN-2026-34
| Source | Role | Status | Size | Groups | Allow | Disallow | Sitemaps |
|---|---|---|---|---|---|---|---|
| self_crawl fetched directly by our own polite crawler |
canonical | dns_error | — | — | — | — | — |
CC-MAIN-2026-30
| Source | Role | Status | Size | Groups | Allow | Disallow | Sitemaps |
|---|---|---|---|---|---|---|---|
| self_crawl fetched directly by our own polite crawler |
canonical | connect_error | — | — | — | — | — |