There may be a connection with boogle, whatever the ### that is. On consecutive days in October, I met testitest (test@testitest.com) from 54.172.81.194 followed by testitest (test@boogle.com) from 54.159.105.152.
Elsewhere that month there was a flurry of requests from assorted 52. and 54. IPs from an ever-changing series of UAs that mostly appear to have been generated by the botrunner's cat: 54.162.218.128 weqrqwer 52.91.172.217 asdfasf 54.208.127.68 sdfasdfasf 54.86.54.63 erhsh 52.23.203.59 TestiTesti 54.226.118.89 MrTest 54.208.60.132 eeer444 54.88.131.155 werer333 52.90.195.200 sadfsafd 52.90.241.238 sadfasdfsadf
I've assumed these are all the same underlying robot because the overall request patterns were always the same. If it weren't for the IPs (commercial server ranges, afaik), I would also have assumed the whole thing was a computer-science class assignment.
Based on the request pattern, they're probably robots.txt compliant. Not that it does them any good if they don't stick around long enough for me to verify behavior and poke holes.
keyplyr
10:58 am on Nov 17, 2016 (gmt 0)
Just looks like typical dynamic cloud hosting, where depending on the amount of leased nodes, the instances will seemingly bounce around.
SomeRandom
5:10 pm on Jan 6, 2017 (gmt 0)
See also the related thread titled BoogleBot [webmasterworld.com]. For the record, this bot is not related to boogle.com.
