Did not request robots.txt file. Banned itself by disobeying robots.txt standard directives.
Sample access log entry: 18.104.22.168 - - [27/Sep/2013:23:59:14 -0400] "GET / HTTP/1.1" 403 362 "-" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; CrawlDaddy v0.3.0 abot v22.214.171.124 http*://code.google.com/p/abot)" Note:Asterisk (*) added by me to disable hot linking the above URL in this message.
Came from two remote host IPs: 126.96.36.199 188.8.131.52
The remote host IPs are owned by GoDaddy.com, LLC (GODAD).
The user of the two remote host IPs also attempted to find WordPress vulnerabilities. Here is a sample access log entry: 184.108.40.206 - - [27/Sep/2013:23:59:12 -0400] "GET /wp-login.php HTTP/1.1" 403 366 "-" "User-Agent\tMozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)"
GoDaddy is a Hosting company, they can never send any visitors as they don't provide Internet Services like, say, Verizon does so it is generally safe to block Hosting companies' full range unless some script services you use are hosted there.
I do have them blocked across all sites. From your observations on what they were doing, I'd just block the whole 220.127.116.11/19 GODaddy range.