OtherYandex reviewed September 2026

YandexAdNet

Yandex operates YandexAdNet, which it describes only as the Yandex Advertising Network robot. Yandex says it takes general robots.txt rules into account, and site owners can also address it with the token YandexAdNet. Yandex publishes no IP range list; verification is forward-confirmed reverse DNS to yandex.ru, yandex.net or yandex.com, or the Yandex Webmaster IP check tool.

OperatorYandex
User-agent tokenYandexAdNet
PurposeOther
robots.txt tokenYandexAdNet
Honors robots.txtYes, per the operator
Published IP rangesNo official range file
VerificationReverse 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 suffixyandex.ru, yandex.net, yandex.com
Full user-agent example (from the operator)Mozilla/5.0 (compatible; YandexAdNet/1.0; +http://yandex.com/bots)

What YandexAdNet does

YandexAdNet shows up in logs as Mozilla/5.0 (compatible; YandexAdNet/1.0; +http://yandex.com/bots). The Yandex documentation gives a one-line description, the Yandex Advertising Network robot, and nothing more. It does not say which pages the robot fetches, how often it visits, whether it executes JavaScript, or what the Advertising Network does with the fetched content. The only thing the documentation ties the visits to is the Yandex Advertising Network, so a site owner has the name alone to explain them.

Yandex states that YandexAdNet takes general robots.txt rules into account, so a Disallow for all user agents covers it, and a group naming User-agent: YandexAdNet applies to it alone. Beyond stopping the robot's requests, the documentation does not spell out what blocking changes for a site, and Yandex does not describe the consequence for a site that takes part in the Yandex Advertising Network. There is no published IP range list for the robot, so verification relies on the same reverse DNS check Yandex documents for all its robots, plus the IP address check tool in Yandex Webmaster.

Operator note. It takes into account the general rules in robots.txt.

Controlling YandexAdNet with robots.txt

Use the token YandexAdNet in robots.txt. Yandex documents that YandexAdNet honors robots.txt directives.

Block everything
User-agent: YandexAdNet
Disallow: /
Allow everything
User-agent: YandexAdNet
Allow: /

Verifying a request is really YandexAdNet

Anyone can put YandexAdNet 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.

Reverse DNS check
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>

Common questions

Should I block YandexAdNet?

Yandex documents it only as the Yandex Advertising Network robot, so the answer depends on whether your site has anything to do with that network. Yandex says the robot follows general robots.txt rules, so a site-wide Disallow stops it, and a User-agent: YandexAdNet group with Disallow: / blocks it alone without affecting other Yandex robots.

How do I verify YandexAdNet?

Do a reverse DNS lookup on the requesting IP and confirm the host name ends in yandex.ru, yandex.net or yandex.com, then resolve that name forward and check it returns the same IP. Yandex also has an IP address check tool in Yandex Webmaster. Yandex publishes no IP range list for YandexAdNet.

What does YandexAdNet do on my site?

The operator's documentation does not say beyond calling it the Yandex Advertising Network robot. Yandex does not describe which pages it requests, how often, or what the fetched content is used for within the Advertising Network.

Sources

Every fact on this page was checked against Yandex's own documentation, listed below, and re-checked by a second reviewer before publication. Reviewed September 2026.

Related crawlers

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.