Home / Sites / examiner.com

How examiner.com treats AI agents

Challenged. Last checked 25 October 2026.

examiner.com puts a Cloudflare bot challenge in front of plain HTTP clients: robots.txt restricts some paths, publishes a feed at /feed/. Agents should read /feed/ instead of scraping.

Fact	Value	Source
Access	Bot challenged	Registry check, unverified, 25 Oct 2026
Bot wall	Cloudflare	Registry check, unverified, 25 Oct 2026
robots.txt	Restricts some paths	Registry check, unverified, 25 Oct 2026
Machine interface	Feed at /feed/	Registry check, unverified, 25 Oct 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 examiner.com block AI bots?

Yes. examiner.com puts a Cloudflare bot challenge in front of plain HTTP clients.

Does examiner.com have an llms.txt?

No llms.txt was found.

Does examiner.com use a bot wall?

Yes, a Cloudflare challenge.

How should an agent fetch examiner.com?

Agents should read /feed/ instead of scraping.

Use this from an agent

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