Home / Sites / mobile.de

How mobile.de treats AI agents

Challenged. Last checked 24 October 2026.

mobile.de puts an Akamai bot challenge in front of plain HTTP clients: robots.txt restricts some paths. Agents need a real browser to fetch it.

Fact	Value	Source
Access	Bot challenged	Registry check, unverified, 24 Oct 2026
Bot wall	Akamai	Registry check, unverified, 24 Oct 2026
robots.txt	Restricts some paths	Registry check, unverified, 24 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

Sites behind an Akamai bot challenge

Questions

Does mobile.de block AI bots?

Yes. mobile.de puts an Akamai bot challenge in front of plain HTTP clients.

Does mobile.de use a bot wall?

Yes, an Akamai challenge.

How should an agent fetch mobile.de?

Agents need a real browser to fetch it.

Use this from an agent

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