ipapi.gr

Bot signals — Search & SEO crawler

Verify YandexBot by reverse DNS

Yandex documents reverse DNS ending in yandex.ru, yandex.net or yandex.com plus a matching forward lookup as the way to verify all Yandex robots. Any forward-confirmed host under these suffixes is treated as Yandex robot infrastructure, as Yandex instructs; it is not proof of an individual request's purpose.

risk.is_crawler rDNS Reviewed
Official documentation (opens in a new tab) All search & SEO crawlers

Check an IP

Is this IP really YandexBot?

Checks the address against what YandexBot publishes, the same evidence behind risk.is_crawler.

01 — Verification

How IPAPI.GR verifies YandexBot.

Only from what YandexBot publishes about itself. No third-party blocklists, no behavioural guesses.

YandexBot

risk.is_crawler
Method
rDNS Forward-confirmed reverse DNS
Reverse DNS
PTR hostname must end in .yandex.ru, .yandex.net or .yandex.com. The hostname must then resolve forward to the same address.
Refresh
Checked when the address is looked up; a confirmed result is reused for up to an hour.

02 — In the response

What a match looks like.

A lookup of a YandexBot address sets risk.is_crawler. The flags come with geolocation and network data in the same response, for Pro API keys.

The response says which kind of bot an address belongs to, not which operator. Pair it with the user agent: a request that claims to be YandexBot but doesn't match is unverified.

GET /api/lookup/{ip}?key=PRO_KEY
{
  // … location and network fields …
  "risk": {
    "is_ai": false,
    "is_crawler": true,
    "is_scanner": false
  }
}

03 — Questions

About YandexBot.

How do I verify YandexBot with reverse DNS?

Look up the PTR record for the IP address. The hostname must end in .yandex.ru, end in .yandex.net and end in .yandex.com, and a forward lookup of that hostname must return the same IP address. A PTR record alone can be set by anyone who controls the address, so the forward confirmation is the part that matters.

Which risk flag does YandexBot set?

A matching address sets risk.is_crawler in the lookup response. The risk flags are returned for Pro API keys.

From the blog

Go deeper.

Related operators

Every operator on the coverage page →

Verify YandexBot on every request.

Pro: 40,000,000 requests a day with is_ai, is_crawler and is_scanner in every lookup.

See Pro Start free