Yandex IP Ranges
Yandex runs its own network for its search engine and the rest of its consumer products, registered with the RIPE NCC as AS13238 to Yandex LLC since 5 September 2002, with the as-name simply YANDEX. Its public cloud business is a separate company on a separate ASN, so an address originated by AS13238 is not a paying customer's server - it is Yandex's own infrastructure.
- Provider
- Yandex
- Primary ASN
- AS13238
- Category
- Tech
- Headquarters
- Moscow, Russia
- Announced IPv4 prefixes
- 31
- Registry
- RIPE
Known IP ranges
These prefixes are currently announced to the global routing table by AS13238 (YANDEX YANDEX LLC). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
95.108.128.0/17
37.9.64.0/18
141.8.128.0/18
37.140.128.0/18
5.45.192.0/18
77.88.0.0/18
5.255.192.0/18
93.158.128.0/18
178.154.128.0/19
84.252.160.0/19
2a02:6b8::/29
2a02:6b8::/32
2a02:6b8:23::/48 (IPv6)
What does a Yandex IP mean in a privacy test?
Seeing a Yandex address in a lookup means the connection reached one of Yandex's own systems directly - the search crawler, a mail server, an API back end - rather than a home or business ISP line. It does not mean the connection touched Yandex Cloud: that is a separate company on a separate ASN, and no part of AS13238's space is sold as public hosting, so there is no tenant's machine to account for the way there would be on a hosting range.
yandex.com/ips, and what the registry adds to it
Yandex publishes its own address list at yandex.com/ips: IPv4 and IPv6 CIDR blocks in a flat list, with no breakdown by product the way GitHub's meta endpoint splits its ranges by service. Three of the published blocks - 77.88.0.0/18, 93.158.128.0/18 and 213.180.192.0/19 - are prefixes AS13238 was announcing in the global routing table when this page was checked, which is the cross-check worth doing before trusting a company's own list at face value. RIPE NCC's registry backs it further: AS13238 carries the as-name YANDEX, was created on 5 September 2002 under organisation ORG-YA1-RIPE, and RIPEstat's announced-prefixes data showed 31 IPv4 prefixes and 16 IPv6 prefixes live under it at the time of writing.
What the published page does not do is say which prefix belongs to which product, so it answers whether an address is Yandex's own space, not whether it is specifically the search crawler. For that narrower question, Yandex's own webmaster documentation gives a different method entirely, and says outright that it does not disclose the crawler's address list - the robots run from several Yandex networks, AS13238 among them, on addresses it says change constantly. The documented check is reverse DNS: look up the address, confirm the hostname ends in yandex.ru, yandex.net or yandex.com, then look that hostname up forward and confirm it resolves back to the same address. Yandex recommends this forward-confirmed check over a static IP list specifically because, in its own words, it is more resistant to changes in Yandex's internal networks.
Why AS13238 is not Yandex Cloud
Every prefix AS13238 originates is Yandex's own address space. All 31 IPv4 prefixes RIPEstat shows announced under it fall inside allocations held by ORG-YA1-RIPE, Yandex LLC, and none of the sub-assignments inside them are leased or resold to an outside customer the way a hosting or cloud range would be - the one assignment registered to a different organisation, a /25 inside 5.45.192.0/18, belongs to Yandex.Taxi B.V., another Yandex group entity. An address originated by AS13238 is therefore Yandex's own system, not a tenant running on Yandex's infrastructure. The ASN does carry transit for a handful of downstream networks, including ICANN's IMRS root-server instance, but those announce their own address space under their own ASNs, not under AS13238.
The catch is that Yandex is not only AS13238. Yandex Cloud, the company's public cloud business, is registered with the RIPE NCC under a separate organisation, ORG-YL62-RIPE, Yandex.Cloud LLC, with its own ASN, AS200350, which was announcing 53 IPv4 prefixes when this page was checked against AS13238's 31. A virtual machine rented from Yandex Cloud answers from that network, not from AS13238, and carries exactly the ambiguity AS13238 does not: it could be Yandex's own workload or any customer's. Nor are those two the whole map - Yandex's own webmaster documentation names further Yandex-run ASNs its crawlers use, so AS13238 and AS200350 are the two that matter for the hosting question, not a complete list of the company's networks. Reading the ASN off an address, rather than assuming Yandex ownership from a hostname or a WHOIS field that mentions the company name, is what actually separates the two. A block or allow rule written against AS13238 alone will never touch Yandex Cloud traffic, and one written against the company name in a WHOIS record risks catching both networks at once, tenants included.
Related tools
Frequently asked questions
What IP ranges does Yandex use?
Yandex announces its addresses under AS13238, registered with the RIPE NCC to Yandex LLC since 5 September 2002. RIPEstat's announced-prefixes data showed 31 IPv4 prefixes and 16 IPv6 prefixes live under it at the time of writing, among them 77.88.0.0/18, 93.158.128.0/18 and 213.180.192.0/19. Yandex also publishes the list itself at yandex.com/ips.
Why does a Yandex IP appear in my privacy test?
Most often because the request reached you from one of Yandex's own systems - the search crawler indexing a page, or a Yandex product calling out - rather than from a person browsing through it. AS13238 is not sold as public hosting, so it is not somewhere a VPN or proxy exits from; if you were expecting a VPN address and see AS13238 instead, no tunnel is carrying that traffic.
Does an address on AS13238 prove it belongs to Yandex?
Yes, for addresses AS13238 originates - RIPE NCC registers that ASN to Yandex LLC, its prefixes sit inside Yandex LLC's own allocations, and none of that space is sold as public hosting, so an address the routing table shows originated by AS13238 is Yandex's own system. It does not prove anything about Yandex Cloud, which runs under a different ASN, AS200350, registered to a separate company, Yandex.Cloud LLC - a customer's server there is not covered by this answer.
How do I check what network a Yandex-looking address belongs to?
Look up the address's ASN and see whether it comes back as AS13238, Yandex's own network, or AS200350, Yandex Cloud, where customers run servers. Those two are what matter for that question, though Yandex runs other ASNs besides them. A WHOIS or RDAP query against the address returns the registered network directly, and RIPEstat's data pages carry the same registry record with the routing detail beside it. For the specific case of a crawler claiming to be Yandex, a forward-confirmed reverse DNS lookup is the check Yandex itself recommends, ahead of trusting the address alone.
What does a Yandex IP address not prove?
That the address is the search crawler specifically, or any other single Yandex product. yandex.com/ips lists ranges as one flat block with no breakdown by service, and Yandex's webmaster documentation says it does not publish the crawler's own address list at all, so the strongest claim an unconfirmed AS13238 address supports is that it is some Yandex system, not a named product - narrowing it to YandexBot requires the forward-confirmed reverse DNS check described above, not the IP list alone.