Welcome to WebmasterWorld Guest from 54.225.58.238

Forum Moderators: Ocean10000 & incrediBILL & keyplyr

Message Too Old, No Replies

Yandex translate

     
9:44 pm on Dec 30, 2012 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member lucy24 is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:Apr 9, 2011
posts:13210
votes: 347


Whether you approve of translation or not, you need to know where they live. Found this one recently:

130.193.62.87 - - [29/Dec/2012:08:17:41 -0800] "GET / HTTP/1.1" 200 5537 "-" "Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.12 Yandex.Translate" 
185.8.cc.dd - - [29/Dec/2012:08:17:42 -0800] "GET /piwik/piwik.js HTTP/1.1" 200 21928 "http:/ /translate.yandex.net/tr-url/en-ru.ru/www.example.com/" "Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.12"
185.8.cc.dd - - [29/Dec/2012:08:17:42 -0800] "GET /images/lion.gif HTTP/1.1" 200 2885 "{as above}" "{as above}"
{et cetera}


The IP was a new one on me; looks like
130.193.32.0/19
belongs to Yandex. The other one is the human, in one of those newly settled RIPE regions. Came through as Russia, as it should.

In logs it's pretty much the same pattern as google translate: Page request comes from search engine IP, blank referer, "Translate" at end of human UA. (For Russia I am fully prepared to believe Opera 9.80. Heck, I've met humans from northern Canada using every edition of Firefox back to 3.0.) All subsidiary pages come from the human IP and UA, with "translate" as part of the referer.

:: now back to irritable grumbling because G### Preview started running from 66.249 some time last month when I wasn't paying attention, and this appears to have some connection with all those referer-less iPad image hits ::
6:19 am on Dec 31, 2012 (gmt 0)

Administrator from US 

WebmasterWorld Administrator not2easy is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:Dec 27, 2006
posts:2764
votes: 64


Related but not: I am seeing UA Opera/9.80 (Windows NT 6.1; U; ru) Presto/2.8.131 Version/11.10 showing up in logs on WP login attempts. I am just adding these to my blocks so it jumped out.

37.1.222.nnn - -"POST /wp-login.php HTTP/1.0" 301 719 "http://example.com/wp-login.php"
"Opera/9.80 (Windows NT 6.1; U; ru) Presto/2.8.131 Version/11.10"

91.224.160.nn - -"POST /wp-login.php HTTP/1.0" 301 721 "http://example.com/wp-login.php"
"Opera/9.80 (Windows NT 6.1; U; ru) Presto/2.8.131 Version/11.10"

188.143.233.n - -"POST /wp-login.php HTTP/1.0" 301 720 "http://example.com/wp-login.php"
"Opera/9.80 (Windows NT 6.1; U; ru) Presto/2.8.131 Version/11.10"

IPs are from DE, NL and RU

Maybe there is an Opera 9.80 Fan Club?
4:04 pm on Jan 3, 2013 (gmt 0)

Junior Member

10+ Year Member

joined:Apr 13, 2005
posts: 128
votes: 0


Wait - not2easy, are these about Yandex Translate or something different? I'm also interested in blocking translate IPs and I just want to be clear on what IP ranges to block.
6:36 pm on Jan 3, 2013 (gmt 0)

Administrator from US 

WebmasterWorld Administrator not2easy is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:Dec 27, 2006
posts:2764
votes: 64


No, those were
showing up in logs on WP login attempts.

I blocked 31.11.128.0/17 (VECTRANET Broadband Poland), 91.224.160.0/23 (Bergdorf Group NL BVI) and 188.143.232.0/23 (IzydorSymanski-net StP RU) as undesirables but not because of Yandex Translate. I posted the information due to a similar and unusual UA on a variety of WP login attempts.