IP Report
95.108.213.132
YANDEX LLC · AS13238 · Moscow (Tsentralnyy administrativnyy okrug), Russia
Score 0 of 100, in the minimal risk band. Bands run 0 to 19 minimal, 20 to 49 low, 50 to 79 medium, 80 to 100 high.
Its risk score of 0/100 is low — nothing in our data suggests this address needs special handling.
Detection signals
Not detected: Tor, VPN, Proxy, Datacenter, Hosting
Summary
95.108.213.132 is crawler infrastructure — automated software that fetches pages, not a person on a browser.
The address is announced by YANDEX LLC (AS13238) and geolocates to Moscow (Tsentralnyy administrativnyy okrug), Moscow, Russia.
Why this address scores 0
It is identified as crawler infrastructure, which explains automated request patterns without implying abuse.
None of that is evidence of wrongdoing on its own, which is why the score stays at 0/100 — these are descriptions of where the address lives, not accusations about what it has done.
Observation history
This address has been looked up through Predax 10 times between August 17, 2026 and September 6, 2026.
Each lookup re-evaluates the address against current feeds, so the classification above reflects its most recent check, not a stale record.
Network & location
- ASN
- AS13238
- Country
- Russia (RU)
- Provider
- YANDEX LLC
- Region
- Moscow
- CIDR
- 95.108.172.0/17
- City
- Moscow (Tsentralnyy administrativnyy okrug)
- Network type
- isp
- PTR
- 95-108-213-132.spider.yandex.com
- First seen
- 8/17/2026, 6:57:41 AM
- Last seen
- 9/6/2026, 6:07:22 PM
- Times seen
- 10
Network context
We have observed 245 addresses on YANDEX LLC (AS13238); 0% of them carried a threat flag or a notable risk score when last checked.
That is a low share, typical of a general-purpose network whose addresses are mostly unremarkable.
What to do with this
If you run a site and this address showed up
This is declared crawler infrastructure, not a visitor. Whether it is welcome is your call: search crawlers usually earn their bandwidth, while others may not.
If it appears in your block log, check which crawler it is before unblocking — blocking a search engine hurts your own site, blocking a scraper does not.
If you want to decide which crawlers may access your site rather than blocking by user agent, the Predax Security plugin for WordPress enforces per-category crawler policy against published IP ranges like the one this address sits in.
If you found this address in your logs
Hits from this address in your logs are automated fetches. The user agent will usually name the bot; verify identity by IP range rather than trusting the header.
Systematic page-by-page access from it is a crawl, not a user session — exclude it from analytics about human behaviour.
Loading map...
Detection sources
No risk signals triggered
This IP didn't match any of our VPN, proxy, Tor, datacenter, or crawler detectors.