curl -s https://www.pathwren.workers.dev/crawler/yandexfavicons.json   # this page, as JSON

No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a

YandexFavicons

Yandex · Search engines · json

User-agent: YandexFavicons
Disallow: /


robots.txt token	`YandexFavicons`
User-agent contains	`YandexFavicons`
Operator	Yandex
Category	Search engines
robots.txt	ignores the * group; obeys rules named for its own token
Verify by	reverse DNS

What it is

Downloads your favicon so Yandex can show it beside your result. Documented as not taking the general robots.txt rules into account.

What blocking it costs you

Your results in Yandex lose their icon. Cosmetic, and a * rule will not achieve it anyway.

Full user-agent string

Mozilla/5.0 (compatible; YandexFavicons/1.0; +http://yandex.com/bots)

Allow it instead

User-agent: YandexFavicons
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=yandexfavicons&s=client-dossiers'

/tools/verification-methods?crawler=yandexfavicons
How do I prove a request really is YandexFavicons? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots
Machine copies: json · markdown
Policies that name this crawler: allow-all · allow-ai-search-only · maximum-ai-visibility