Quick answer
What is YandexTracker?
YandexTracker is a monitoring bot from Yandex used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
Its primary user-agent pattern is YandexTracker; related patterns include YandexTracker Yandex robot; a representative HTTP user-agent is Mozilla/5.0 (compatible; YandexTracker/1.0; +the operator's published verification endpoint).
YandexTracker is verified with High confidence. The identity type is Official Documented, and the evidence basis is official operator documentation.
YandexTracker is marked as respecting robots.txt directives for crawler access control.
YandexTracker can usually be allowed after confirming the source and monitoring request volume.
Identity
How to identify this Bot
- User-Agent
YandexTracker- robots.txt token
YandexTracker- HTTP agent
Mozilla/5.0 (compatibleYandexTracker/1.0+http://yandex.com/bots)- Aliases
YandexTracker Yandex robot- Operator
- Yandex
- Family
- Yandex
- Technical kind
- fetcher
- Identity method
- official-documented
Behavior
Purpose, behavior, and practical context
- Purpose
- monitoring
- Common use
- YandexTracker is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
- Respects robots.txt
- yes
- Spoofing risk
- YandexTracker has medium spoofing risk because the user-agent can be copied, even when the bot has strong source or documentation support.
- Detection notes
- YandexTracker traffic is primarily detected by the `YandexTracker` user-agent pattern; related patterns include `YandexTracker Yandex robot`; a representative HTTP user-agent is `Mozilla/5.0 (compatible; YandexTracker/1.0; +the operator's published verification endpoint)`. Compare source IPs, reverse DNS, request paths, and crawl cadence with Yandex infrastructure before trusting the traffic.
Verification and controls
Verification and blocking guidance
- Verification method
- Verify YandexTracker by matching `YandexTracker` to Yandex evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- General blocking snippet
User-agent: YandexTrackerDisallow: /
Related records