Welcome to WebmasterWorld Guest from 220.127.116.11 , register , free tools , login , search , pro membership , help , library , announcements , recent posts , open posts Become a Pro Member
There's a closed 2013 thread on stremor [ webmasterworld.com] by lucy 18.104.22.168 - - [12/Aug/2014:15:36:41 -0600] "GET /robots.txt HTTP/1.1" 200 1115 "-" "stremorbot AppEngine-Google; (+http://code.google.com/appengine; appid: s~stremor-crawler)" followed by six successive requests for the same page from two slightly different UA's. Returned nine minutes later with four requests for the same page duplicating the slightly different UA's.. "AppEngine-Google; (+http://code.google.com/appengine; appid: s~liquid-helium)"
At my servers, that guy would get blocked by several reasons: 1.) by range: 22.214.171.124/18 Google Cloud 2.) by UA "AppEngine" 3.) by UA "code" 4.) by UA "crawler" ...and I haven't even seen the request headers yet - just say'n :)
At my servers, that guy would get blocked by several reasons: Same for me, however I'd not had the IP range denied until now. Are there more Google Clouds? GOOGLE-CLOUD 2600:1900:: - GOOGLE-CLOUD 126.96.36.199 - 188.8.131.52 184.108.40.206/15 GOOGLE-CLOUD 220.127.116.11 - 18.104.22.168 22.214.171.124/19 GOOGLE-CLOUD 126.96.36.199 - 188.8.131.52 184.108.40.206/18 GOOGLE-CLOUD 220.127.116.11 - 18.104.22.168 22.214.171.124/20 GOOGLE-CLOUD 126.96.36.199 - 188.8.131.52 184.108.40.206/16 GOOGLE-CLOUD 220.127.116.11 - 18.104.22.168 22.214.171.124/17 GOOGLE-CLOUD 126.96.36.199 - 188.8.131.52 184.108.40.206/22 GOOGLE-CLOUD 220.127.116.11 - 18.104.22.168 22.214.171.124/21 GOOGLE-CLOUD 126.96.36.199 - 188.8.131.52 184.108.40.206/20 GOOGLE-CLOUD 220.127.116.11 - 18.104.22.168 22.214.171.124/22 GOOGLE-CLOUD 126.96.36.199 - 188.8.131.52 184.108.40.206/22 GOOGLE-CLOUD 220.127.116.11 - 18.104.22.168 22.214.171.124/21 GOOGLE-CLOUD 126.96.36.199 - 188.8.131.52 184.108.40.206/20 GOOGLE-CLOUD 220.127.116.11 - 18.104.22.168 22.214.171.124/19 GOOGLE-CLOUD 2600:1900:: - 2600:190F:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
I have a few more here: 126.96.36.199 - 188.8.131.52 184.108.40.206/21 220.127.116.11 - 18.104.22.168 22.214.171.124/21 126.96.36.199 - 188.8.131.52 184.108.40.206/21 220.127.116.11 - 18.104.22.168 22.214.171.124/21 126.96.36.199 - 188.8.131.52 184.108.40.206/20 220.127.116.11 - 18.104.22.168 22.214.171.124/18 I am pretty sure there are more. wilderness
Would have never believed that I'd be required to add this complete set of IP's in such a short while. With six of the ranges have been utilized this thread opened, the remaining were completed. keyplyr
Just a FYI - As with most things, these ranges may not be something all webmasters should block. Some of those ranges are used for things that some may find beneficial. For example, this Google Cloud range retrieves the images used when you or someone else posts a link to one of your pages at Google+: 126.96.36.199 - 188.8.131.52 184.108.40.206/20 Having a nice, pretty image to click on brings in a lot more traffic than just a text link. Two more of the above ranges are used by apps (from Google Play) that also may be beneficial to some site owners. Mobile is a huge traffic source and one that should be nurtured, not blocked IMO. Personally, I'm a big fan of incoming traffic.
Personally, I'm a big fan of incoming traffic. As am I. just not from obscured IP's.