Vol. I · Tue, 17 Nov 2026Open 24 hours · Feeding: continuous · Please do not tap the glassPatrons☕ Keepers' coffee
Plate CLVII0x080172D8MOSTLY
Kingdom Automata›Phylum HTTP›Order Scanners›Family Unidentified›Species YandexBot (impostor)
Specimen file · The Feral Pit

YandexBot (impostor)

Ursus fraudulentus

What is YandexBot (impostor)?

Something claiming to be YandexBot that does not come from Yandex's network. It failed reverse-DNS or IP-range verification. It is operated by Unknown and identifies itself as Yandex.

Temperament: shifty. Introduces itself as YandexBot. Yandex has never heard of it.

Operator
Unknown
Conservation status
Selectively obedient
First seen
3 Oct 2026
Last seen
36 min ago
Visits today
7
This week
8
All time
49
Caught in the trap
Never

YandexBot (impostor)'s food bowl

the bowl, as bots see it

The bowl is empty.

5 of 5 tokens left today
§ I.

Identification

Its full user-agent string, exactly as it arrives at the gate:

User-Agent
$ Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)

This is not a real species. It is a costume: requests that use YandexBot's name but fail reverse-DNS or IP-range checks against Yandex's network.

Identity check · logged visits, last 30 days
Claimed to beYandexBot
Failed the check15 times · last 36 min ago

How it was checked: its reverse DNS must end in .yandex.ru or .yandex.net or .yandex.com and resolve back to the same address. Each address is checked when it first visits, and the result is kept for a day.

§ II.

How to block YandexBot (impostor)

YandexBot (impostor) does not read robots.txt, so a polite sign is wasted on it. Refuse it at your web server or firewall instead. User agents are easy to fake, so pair this with rate limiting.

nginx.conf
# robots.txt will not stop YandexBot (impostor). Block it at the server.
# nginx
if ($http_user_agent ~* "Yandex") {
    return 403;
}

The same thing on Apache:

# Apache (.htaccess)
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} Yandex [NC]
RewriteRule .* - [F,L]
§ III.

Observed behaviour

Visits, last 30 dayspeak 7 / day, 17 Nov 2026
19 Oct 2026today
Diet · pages most often eaten
/robots.txt7
/3
/firebase.json1
/serverless.yml1
/key.json1
Visiting hours
00h – 11h12h – 23h

Most active around 17:00. Office hours, like a professional.

robots.txt compliance
38.7%

Requested 30 disallowed pages out of 49 requests. Read robots.txt 7 times.

Trap Room record
Clean

Has never followed the hidden link to /trap/. Either well trained or very lucky.

In the Labyrinth
Level 1,177

Opened 30 rooms in the endless maze. Watch it in the Labyrinth →

§ IV.

Where it comes from

Claims to be YandexBot. Real YandexBot traffic comes from Yandex's own network; these visits came from:

Networks · 2 on file, last 30 days
YANDEX LLC AS1323880%
MOACK.Co.LTD AS13819520%
Countries
Russia RU67%
South Korea KR20%
Germany DE7%
Ukraine UA7%

Networks and countries come from the visitor's IP address, looked up in a local copy of the DB-IP database. The addresses themselves are never stored.

§ V.

Keeper's field notes

17 Nov 202617:10. Arrived without announcement. Consumed /firebase.json and /serverless.yml. Departed.
17 Nov 2026Observed reading robots.txt in full. Complied with every word.
3 Oct 2026First recorded at the gate. Entered in the register as Ursus fraudulentus.
3 Oct 2026Visited 30 times in a single day. Keeper unable to establish why.
§ VI.

Questions site owners ask

Does YandexBot (impostor) respect robots.txt?

Mostly. It reads robots.txt, but it has fetched a disallowed page 30 times out of 49 requests observed here.

Will blocking YandexBot (impostor) hurt my search rankings?

No. Nothing respectable will miss it.

How often does YandexBot (impostor) visit?

Here, about 1 requests a day over the last week. Visits to your site depend on its size, how often it changes, and how many links point to it.

Also in The Feral Pit