How iscorp.com treats AI agents
iscorp.com 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 | Reports | Checked |
|---|---|---|---|---|
| Access posture | bot_challenged | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
| Challenge vendor | cloudflare | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
| Robots posture | allow | 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 | /feed/ | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
Listed in: Sites behind a Cloudflare bot challenge ยท Sites that publish a feed or sitemap
Questions
Does iscorp.com block AI bots?
Yes. iscorp.com puts a Cloudflare bot challenge in front of plain HTTP clients.
Does iscorp.com have an llms.txt?
No llms.txt was found.
Does iscorp.com use a bot wall?
Yes, a Cloudflare challenge.
How should an agent fetch iscorp.com?
Agents should read /feed/ instead of scraping.
Use this from an agent
JSON: /v1/origins/iscorp.com. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.