| 7:34 pm on Aug 24, 2013 (gmt 0)|
Perfectly normal range for yandex, which is originally Russian migrating to American.
I've blocked the yandeximages bot for a lont time - as long as I've enabled yandex, in fact. Again a normal thing.
Check out the URL in the UA - they have a good bot support page.
| 9:44 pm on Aug 24, 2013 (gmt 0)|
Yandex Images counts as "no skin off my nose". I can now recognize the Russian word for "rat" in Cyrillic :)
Their robots page has a good listing of UAs but they've always refused to name IPs. (Although not as bad as, say, Majestic, which tends to get locked out purely because they operate from other people's server farms.)
I don't get any fake yandexbots worth mentioning, but I do get fake "yandsearch" referers. If I ever find their contact address I will ask what, if anything, "lr=213" means.
| 4:24 am on Aug 25, 2013 (gmt 0)|
I see their image bots at 188.8.131.52/19 and 184.108.40.206/18 also.
| 8:21 pm on Aug 25, 2013 (gmt 0)|
Lucy - yandex IPs are fairly easy...
220.127.116.11 - 18.104.22.168
22.214.171.124 - 126.96.36.199
188.8.131.52 - 184.108.40.206
220.127.116.11 - 18.104.22.168
22.214.171.124 - 126.96.36.199
188.8.131.52 - 184.108.40.206
220.127.116.11 - 18.104.22.168
22.214.171.124 - 126.96.36.199
188.8.131.52 - 184.108.40.206
220.127.116.11 - 18.104.22.168
22.214.171.124 - 126.96.36.199
Add new ones as they are discovered. Not all IPs in range claim to be bots but coupled with the actual (acceptible) UA I've found no problems.
Given the current state of SEs in general, yandex is a fairly good one and seems to give good results whilst not annoying webmasters (eg me). Its bots and SEs are based in Russia and USA and I let all their ordinary bots in, excluding image and a few others.
Only a guess but could "lr=213" be a general reference to the bot range that originally discovered it? Maybe not, but a possibility.
| 6:20 am on Aug 26, 2013 (gmt 0)|
The exact string "lr=213" only occurs in fake-referer requests. Most are already blocked by IP; I've retained the referer check just for insurance. I've never seen "lr=any-number-at-all" in a legitimate YandSearch visit; that's what makes it mystifying.
Far as I can tell, I've never seen 213.180 at all, ever, and didn't know the Yandex range existed :) Is this maybe a range Yandex used to crawl from, so "lr=213" is something you'd get in very, very old search results, now only preserved in fake referers?
There are several ranges on your list I've never seen in my life. Contrariwise I've got the 5.255 range noted above, and also 188.8.131.52/18. (184.108.40.206 YandexFavicon gets front page + favicon, 37.9.69-70 YandexImageResizer, UA list says it's for mobiles)
| 12:37 pm on Aug 26, 2013 (gmt 0)|
|The region to give preference to when generating search results is defined by the value of the lr parameter of the search query. |
213 = Moscow
| 1:36 pm on Aug 26, 2013 (gmt 0)|
You're a better man than I, thetrasher. I looked everywhere and never managed to find that.
It must be one of those prefs you can set by default. The overwhelming majority of my lr=213 searches come with a referer string that says in full
OK, so they're looking my domain, but specifically that version of it which is most applicable to Moscow? :)
:: detour to spell out non-213 results (I don't read Cyrillic) ::
Wonder why St Petersburg (which I am sorry to say I still think of as Leningrad) is listed twice?
| 2:11 pm on Aug 30, 2013 (gmt 0)|
Another yandex IP range with some bots. New to me today but no indication in DNS as to when it was registered.
220.127.116.11 - 18.104.22.168
Bots found so far:
probably not all IPs are bots but checked against UA should be safe to enabled all.
Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)
| 8:01 pm on Aug 30, 2013 (gmt 0)|
Did you copy-and-paste the wrong numbers? 22.214.171.124/18 is what we've been talking about all along :)
| 8:21 pm on Aug 31, 2013 (gmt 0)|
I cross-checked the IP in DNS to see what we were talking about and forgot to add it to my database. It was new to me with your original posting: my posting was because I found a bot hitting an IP I hadn't (but should have) logged. :(