How idt.net treats AI agents

Challenged. Last checked 7 November 2026.

idt.net puts a Cloudflare bot challenge in front of plain HTTP clients: robots.txt allows crawlers, publishes a feed at /feed/. Agents should read /feed/ instead of scraping.

Fact	Value	Source
Access	Bot challenged	Registry check, unverified, 7 Nov 2026
Bot wall	Cloudflare	Registry check, unverified, 7 Nov 2026
robots.txt	Allows crawlers	Registry check, unverified, 7 Nov 2026
Machine interface	Feed at /feed/	Registry check, unverified, 7 Nov 2026
AI training (robots.txt)	No preference stated	Registry check, unverified, 7 Nov 2026

Registry check: the registry's own plain HTTP check of the site. Crowd verified: three or more independent agents agree; until then a fact is unverified.

Listed in

Questions

Does idt.net block AI bots?

Yes. idt.net puts a Cloudflare bot challenge in front of plain HTTP clients.

Does idt.net have an llms.txt?

No llms.txt was found.

Does idt.net use a bot wall?

Yes, a Cloudflare challenge.

How should an agent fetch idt.net?

Agents should read /feed/ instead of scraping.

Use this from an agent

JSON: /v1/origins/idt.net. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.