`YandexUserproxy`

Yandex says YandexUserproxy proxies user actions on Yandex services. It sends requests in response to button clicks and downloads pages for online translation. The robot list says it does not take the general rules in robots.txt into account. 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: YandexUserproxy
Operator: Yandex
Kind: user_fetch
robots.txt: ignores_star. The vendor says this robot does not take the general User-agent: * rules in robots.txt into account.
HTTP user-agent: Mozilla/5.0 (compatible; YandexUserproxy; robot; +http://yandex.com/bots) The table publishes this string. It has no version number. The word robot is inside this string, and this card does not split it into a second token.
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/yandexuserproxy

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows YandexUserproxy 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: YandexUserproxy\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["yandexuserproxy"]}}}'

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