robots.txt & llms.txt across the Tranco top 1M
Data as of 2026-09-07 · robots.txt via Common Crawl CC-MAIN-2026-34 + our polite crawl · llms.txt via our polite crawl · Tranco list XN67N (2026-09-03T22:00:02.533886) · 1,000,000 panel domains 1,212,578 robots.txt fetches · 740,113 parsed · 56,498 llms.txt probes

Two public profiles · no score or winner

horny.jetzt and jilsander.com

horny.jetzt #119,301 jilsander.com #119,303

Measured takeaway

horny.jetzt's robots.txt disallows every crawler; jilsander.com's does not.

Measured in Botfy's 2026-09-07 publication.

At a glance

A difference appears only when both sites have comparable evidence. Unavailable or unresolved observations remain incomplete.

Evidencehorny.jetzt jilsander.com
robots.txt Served and parsed Served and parsed
Google crawl posture Blocked Open
Unnamed crawler fallback Blocked the wildcard (*) group disallows everything, so they are blocked without being named Partly Restricted they inherit the wildcard (*) group's rules
Base /llms.txt Not probed Not found when probed

Treatment by purpose

Only resolved blocked, allowed, or mixed states count as a policy agreement or difference. Unnamed agents still inherit each site's wildcard rules.

Declared purposehorny.jetzt jilsander.com
Model training Not explicitly addressed Mixed
AI search Not explicitly addressed Allowed
Live assistant fetch Not explicitly addressed Allowed
Opt-out directives Not explicitly addressed Allowed
Ambiguous / undocumented Not explicitly addressed Mixed

Named agents

Measured differences appear first. “Not explicitly addressed” is not the same as allowed; the site's wildcard fallback governs that crawler.

Agenthorny.jetzt jilsander.com
GPTBot OpenAI Not explicitly addressed Allowed
ClaudeBot Anthropic Not explicitly addressed Allowed
CCBot Common Crawl Not explicitly addressed Allowed
Bytespider ByteDance Not explicitly addressed Blocked
Applebot Apple Not explicitly addressed Allowed
PerplexityBot Perplexity Not explicitly addressed Allowed
YouBot You.com Not explicitly addressed Allowed
Amazonbot Amazon Not explicitly addressed Allowed
Google-Extended Google Not explicitly addressed Allowed
GoogleOther Google Not explicitly addressed Allowed
Scrapy Scrapy Not explicitly addressed Blocked

How each site compares with its own rank peers

The sites may belong to different rank bands. Each percentage keeps its own population and denominator; Botfy does not subtract rates from unlike cohorts.

Traithorny.jetzt jilsander.com
Wildcard group Yes 89.6% Ranks 100,001–1,000,000 · n=680,000 Yes 89.6% Ranks 100,001–1,000,000 · n=680,000
Effectively open file No 26.0% Ranks 100,001–1,000,000 · n=680,000 No 26.0% Ranks 100,001–1,000,000 · n=680,000
Sitemap declared No 60.6% Ranks 100,001–1,000,000 · n=680,000 Yes 60.6% Ranks 100,001–1,000,000 · n=680,000
robots.txt served Yes 61.8% Ranks 100,001–1,000,000 · n=1,111,034 Yes 61.8% Ranks 100,001–1,000,000 · n=1,111,034
robots.txt returned 404 No 8.5% Ranks 100,001–1,000,000 · n=1,111,034 No 8.5% Ranks 100,001–1,000,000 · n=1,111,034
Over the RFC parse limit No 0.3% Ranks 100,001–1,000,000 · n=680,000 No 0.3% Ranks 100,001–1,000,000 · n=680,000
Blanket disallow Yes 10.8% Ranks 100,001–1,000,000 · n=680,000 No 10.8% Ranks 100,001–1,000,000 · n=680,000
How this comparison is measured

Both sites use Botfy's latest published observations. A missing fetch, unresolved agent verdict, and measured absence are different states. Peer percentages use each site's exclusive Tranco rank band and print their own denominator. Populations, sources, and limits →

Keep comparing

Each suggestion replaces one side using an editorial collection or current rank proximity. Neither means the sites have similar policies.