Gimme60bot

[lucy24]

Anyone know anything? It started showing up about a week ago from assorted Verizon ranges in the upper 71 area:

71.189.164.218 - - [17/May/2014:10:09:58 -0700] "GET /robots.txt HTTP/1.0" 200 802 "-" "Mozilla/5.0 (compatible; Gimme60bot/1.0; +http://gimme60.com)" 

71.177.184.59 - - [17/May/2014:09:33:09 -0700] "GET /robots.txt HTTP/1.0" 200 848 "-" "Mozilla/5.0 (compatible; Gimme60bot/1.0; +http://gimme60.com)" 

Those are two different sites-- the first appearance on each.

Currently it's asking for robots.txt with almost bing-like enthusiasm. But it first did something that annoys me a bit (here quoting from a third site because logs happened to be handy, but each site started the same way):

71.177.184.59 - - [16/May/2014:20:07:05 -0700] "GET / HTTP/1.0" 200 2321 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0" 
71.177.184.59 - - [17/May/2014:10:15:26 -0700] "GET /robots.txt HTTP/1.0" 200 302 "-" "Mozilla/5.0 (compatible; Gimme60bot/1.0; +http://gimme60.com)" 

Humanoid UA, visiting long before its first robots.txt request. Why?

Sometimes it forgets to capitalize itself, but otherwise the robotic and humnoid UAs are each consistent.

The Verizon IP makes it a pain to block unless I resort to UA-based lockouts; there are humans in the immediate neighborhood. Is it worth blocking? What does it want?

[not2easy]

I found it crawling last August:

71.177.184.59 - - [16/Aug/2013:15:09:33 -0500] "GET / HTTP/1.0" 301 229 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0"

Lucky for me it was on a site where everyone is blocked. The HTTP/1.0 part called attention to it and I had no issue in blocking Verizon for that site. I see it is still on Firefox/16.0 at least. A different neighbor has a

SetEnvIf Remote_Addr ^71\.246\.206\.127$ block

on a different site.

[keyplyr]

robots.txt seems to stop it.

Looks like a distro bot with unknown mission. Probably legit, or else why would it obey robots.txt?

[lucy24]

robots.txt seems to stop it

Well, except for the preliminary visit where it has not yet seen robots.txt. Hence the annoyance :(

I found it crawling last August:

Huh. I know I've seen the exact IP before, but I didn't realize it was the identical (humanoid) UA.