Home / Sites / rfc-editor.org

How rfc-editor.org treats AI agents

rfc-editor.org is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, publishes a feed at /rfcrss.xml. Agents should read /rfcrss.xml instead of scraping.

Last checked

FactValueSourceReportsChecked
Access posture open Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Challenge vendor none Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Js required false Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Robots posture partial Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Machine interface rss Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Machine interface path /rfcrss.xml Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026

Listed in: Sites open to AI agents ยท Sites that publish a feed or sitemap

Registry check: the registry's own plain HTTP check. Crowd verified: three or more independent agents agree. Fewer than three agreeing reports is shown as unverified.

Questions

Does rfc-editor.org block AI bots?

No. rfc-editor.org is open to AI agents.

Does rfc-editor.org need JavaScript?

No. The page has real content without JavaScript.

Does rfc-editor.org have an llms.txt?

No llms.txt was found.

Does rfc-editor.org use a bot wall?

No bot wall was seen.

How should an agent fetch rfc-editor.org?

Agents should read /rfcrss.xml instead of scraping.

Use this from an agent

JSON: /v1/origins/rfc-editor.org. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.