`YandexBot`

Yandex says YandexBot is the main indexing robot and that it takes the general rules in robots.txt into account. The MirrorDetector string is this token, not a separate card. The robot list says an agreement between Yandex and the site owner can override some robots.txt restrictions. This check does not apply that agreement.

robots.txt token: YandexBot
Operator: Yandex
Kind: search
robots.txt: obeys. The vendor says this crawler obeys robots.txt on automatic crawls.
HTTP user-agent: Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots) The table publishes this string for the main indexing robot. The same table lists Mozilla/5.0 (compatible; YandexBot/3.0; MirrorDetector; +http://yandex.com/bots) for determining alternate addresses. That string also contains YandexBot, and this card does not split it into a second token. A log example on the page adds a browser version after the table string and says that version may change.
IP list: None on the cited page. This page says the IP list is not disclosed.
Source: How to check that a robot belongs to Yandex. Retrieved 2026-10-18.

JSON

curl -s https://whosthatbot.com/v1/crawlers/yandexbot

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows YandexBot on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: YandexBot\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["yandexbot"]}}}'

That call returns fetched_target false. This row is disallow via group YandexBot, rule Disallow: /.