Search engine crawler · Yandex
YaComBot user agent, IP ranges and robots.txt
YaComBot is Yandex's search engine crawler. It identifies itself with the YaComBot user-agent token, honors robots.txt according to its operator, and can be verified by reverse DNS (yandex.ru, yandex.net, yandex.com).
- Operator
- Yandex
- Reviewed
- September 2026
- Sources
- 1
- Operator
- Yandex
- User-agent token
- YaComBot
- Purpose
- Search engine crawler
- robots.txt token
- YaComBot
- Honors robots.txt
- Yes, per the operator
- Published IP ranges
- No official range file
- Verification
- Reverse DNS lookup on the requesting IP must return a host ending in yandex.ru, yandex.net or yandex.com, and a forward DNS lookup of that host must return the same IP. Yandex Webmaster also provides an IP address check tool.
- Reverse DNS suffix
- yandex.ru, yandex.net, yandex.com
- Full user-agent example
- Mozilla/5.0 (compatible; YaComBot/3.0; +http://ya.cc/bots)
Block or allow YaComBot in robots.txt
User-agent: YaComBot
Disallow: /User-agent: YaComBot
Allow: /Verify a request is really YaComBot
Anyone can put YaComBot in a User-Agent header. Reverse DNS lookup on the requesting IP must return a host ending in yandex.ru, yandex.net or yandex.com, and a forward DNS lookup of that host must return the same IP. Yandex Webmaster also provides an IP address check tool.
host <request-ip>
# expect a hostname ending in yandex.ru, yandex.net, yandex.com
host <that-hostname>
# expect it to resolve back to <request-ip>What YaComBot does
Yandex operates YaComBot, a search indexing robot that, like YandexComBot, indexes content for the non-Russian-speaking segment of Yandex search. It takes robots.txt directives into account like the main YandexBot, under the token YaComBot. Verify it with reverse DNS on a yandex.ru, yandex.net or yandex.com hostname, confirmed by forward DNS; Yandex publishes no IP list for it.
In logs the robot appears as "Mozilla/5.0 (compatible; YaComBot/3.0; +http://ya.cc/bots)". Yandex describes it in the Russian-language edition of its robot reference as working by analogy with YandexComBot, indexing content for the non-Russian-speaking search segment. The robot takes robots.txt directives into account in the same way as the main YandexBot, and the general rules column for it reads Yes.
Allowing YaComBot keeps a site available for indexing in the part of Yandex search aimed at non-Russian-speaking users. Blocking it with a User-agent: YaComBot directive removes pages from that index but does not affect other Yandex robots, which have their own tokens. Because the robot takes the general User-agent: * rules into account, an existing site-wide disallow already applies to it without a dedicated block. Yandex does not document crawl rate or JavaScript execution for this robot. It publishes no IP range list either, so verification is by hostname.
Operator note. Yandex's Russian-language documentation describes it as: 'По аналогии с YandexComBot индексирует контент для нерусскоговорящего сегмента поиска. Учитывает директивы в robots.txt, как основной YandexBot.' It takes into account the general rules in robots.txt (Да).
Common questions
- How do I verify YaComBot?
- Run a reverse DNS lookup on the requesting IP and check that the hostname ends in yandex.ru, yandex.net or yandex.com, then run a forward DNS lookup on that hostname and confirm it returns the same IP. Yandex also has an IP address check tool in Yandex Webmaster. Yandex publishes no IP range list.
- Should I block YaComBot?
- Only if you do not want your pages indexed for Yandex's non-Russian-speaking search segment. The robot takes robots.txt directives into account, so a User-agent: YaComBot disallow is enough. Blocking it leaves YandexBot and the other Yandex robots unaffected, since each has its own token.
- Does YaComBot run JavaScript?
- Yandex's documentation for this robot does not say. The Russian-language entry describes only its purpose and its robots.txt behaviour, so there is no operator statement about whether it renders pages or executes scripts.
Sources
The operator documentation used for this entry. Recorded review date September 2026; consult the linked pages for current policy and compare them with this dated snapshot.
This registry documents how operators describe their own bots so site owners can identify and control them. It does not publish third-party IP lists or guess at undocumented behaviour. To see how your own site responds to automated visitors, the bot detection scanner reads a URL's live response and names the protection it finds.