YandexBot IP addresses

YandexBot at a glance

How to verify a visitor is YandexBot

Look up the PTR record of the request's source address and confirm the name ends in yandex.ru or yandex.net or yandex.com. Then resolve that name forward and confirm one of its addresses is the address you started from — a PTR record alone can be set to anything by whoever controls the reverse zone, and the forward confirmation is what makes it proof. Yandex documents this check as the way to verify YandexBot.

What the API answers for one of its addresses

A lookup of an address whose verified hostname sits under those domains answers is_crawler true, names it in crawler and classes it in crawler_kind. A crawler carries no risk weight, and the datacenter weight is skipped for it: its operator is known and its infrastructure is the point. The hostname check is a live DNS query, so it runs only when the lookup asks for it with hostname: true.

curl https://spaw.co/api/v1/ip \
  -H "Authorization: Bearer $SPAW_KEY" \
  -H "Content-Type: application/json" \
  -d '{"ip": "203.0.113.9", "hostname": true}'

"is_crawler": true,
"crawler": "YandexBot",
"crawler_kind": "search",
"risk_signals": [{ "signal": "datacenter", "weight": 0, "dataset": "datacenter-ranges" }]

A range proves the operator, not intent. Whether YandexBot is welcome on a site is a robots.txt decision; this page and the lookup only settle whether a request that says it is YandexBot really came from Yandex.

Other crawlers

• Googlebot
• Google special crawlers
• Google user-triggered fetchers
• Google user-triggered fetchers
• Bingbot
• GPTBot
• ChatGPT-User
• OAI-SearchBot
• PerplexityBot
• Perplexity-User
• DuckDuckBot
• AhrefsBot
• Applebot
• Baiduspider
• Every crawler
• Look up any address

crawler-ranges reverse DNS, no file · checked 2026-09-13