Is YandexBot using 87.250.224.237?
Yes, 87.250.224.237 is a confirmed YandexBot IP address from which YandexBot crawls the world wide web.
Status
Current
Last Seen
July 14, 2026, 05:25
IPv4
87.250.224.237
Host
87-250-224-237.spider.yandex.com.
User Agents Detected Crawling from YandexBot IP 87.250.224.237
- Mozilla/5.0 (compatible; YandexAccessibilityBot/3.0; +http://yandex.com/bots) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0
- Mozilla/5.0 (compatible; YaDirectFetcher/1.0; +http://yandex.com/bots)
- Mozilla/5.0 (compatible; YandexMetrika/2.0; +http://yandex.com/bots yabs01)
- Mozilla/5.0 (compatible; YandexMetrika/4.0; +http://yandex.com/bots)
- Cloud-CDN-Google (GFE/2.0)
- Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)
- Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0
- Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.268
- Mozilla/5.0 (compatible; YandexFavicons/1.0; +http://yandex.com/bots)
- Mozilla/5.0 (compatible; YandexImages/3.0; +http://yandex.com/bots)
- Mozilla/5.0 (iPhone; CPU iPhone OS 15_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.4 Mobile/15E148 Safari/604.1 (compatible; YandexMobileBot/3.0; +http://yandex.com/bots)
- Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.2 Mobile/15E148 Safari/604.1 (compatible; YandexMobileBot/3.0; +http://yandex.com/bots)
- Mozilla/5.0 (compatible; YandexRCA/1.0; +http://yandex.com/bots)
- Mozilla/5.0 (compatible; YandexMarket/2.0; +http://yandex.com/bots)
- Mozilla/5.0 (compatible; YandexRenderResourcesBot/1.0; +http://yandex.com/bots) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0
Current and historic YandexBot IP addresses
Every IP address in the YandexBot API carries a status. A current IP address was confirmed within the past 12 months, through observed crawl activity or through the IP address lists published by the bot operator. A historic IP address has older confirmations only.
Historic records stay in the database on purpose. Log file analysis often covers older date ranges, and a lookup on aged logs still needs a match for the IP addresses in use back then.