TweetedTimes Now on Yandex?

[incrediBILL]

I noticed this before but was too lazy to post it:

100.43.81.9
Mozilla/5.0 (compatible; TweetedTimes Bot/1.0; +http://tweetedtimes.com)

IP Range: 100.43.64.0 - 100.43.95.255
ORG: Yandex Inc

They used to crawl from comcastbusiness not too long ago per Pfui:
[webmasterworld.com...]

[GaryK]

Weren't they bought by Yandex about a year ago?

[dstiles]

Thanks for the heads-up, Bill.

I had a few IPs in the range 7 - 11 hit by something in June - only minor hits but your posting brought them to my notice. I've now blocked the range 100.43.81/24 - can't block the whole IP range because there are real (US) yandex bots on 100.43.83.129 - 100.43.83.161.

[incrediBILL]

can't block the whole IP range because there are real (US) yandex bots on 100.43.83.129 - 100.43.83.161.

Sure you can.

You block the whole range then punch holes in the firewall only if it's a Yandex bot.

I do the same thing with Google, I block the entire Google range and open holes in the firewall just for the stuff I want so a ton of stuff from their ranges goes bouncing off my servers on a regular basis.

I wouldn't have to do that if the crawlers wouldn't mix the usage of their IPs and/or properly label the user agents for other IP activities or set the rDNS, but they don't so BLOCK.

[keyplyr]

Unlike Google, Yandex leases subnets to business who may then release some for private use.

[incrediBILL]

Yandex leases subnets to business who may then release some for private use.

How sad for them :)

[dstiles]

Bill, yes, I know, that's what I do (although I do not currently 403 the parent range; I have a special by-pass within it for bots). I was being literately lazy. Sorry. :)