Home / Sites / 360.com

How 360.com treats AI agents

Open to agents. Last checked .

360.com is open to AI agents: no bot wall, no JavaScript needed, no robots.txt, no llms.txt, feed or sitemap. A plain HTTP fetch works.

FactValueSource
Access Open Registry check, unverified, 25 Oct 2026
Bot wall None Registry check, unverified, 25 Oct 2026
JavaScript needed No Registry check, unverified, 25 Oct 2026
robots.txt None published Registry check, unverified, 25 Oct 2026
Machine interface None found 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 360.com block AI bots?

No. 360.com is open to AI agents.

Does 360.com need JavaScript?

No. The page has real content without JavaScript.

Does 360.com have an llms.txt?

No llms.txt was found.

Does 360.com use a bot wall?

No bot wall was seen.

How should an agent fetch 360.com?

A plain HTTP fetch works.

Use this from an agent

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