"PostRank/2.0 (postrank.com)" hits my sites, files and root, only via two amazonaws.com Hosts and then only in a Twitter swarm. It never asks for robots.txt, is always undeterred by 403s, and only hits via HEAD.
When it hits, it's to the same file in multiples of four or eight hits, often many times a day. Here's a small example 'set' of hits, one of 26-plus, post-tweet sets this month:
ec2-204-236-254-109.compute-1.amazonaws.com [05 Nov: 22:22:49] HEAD /dir1/file1.html
ec2-204-236-254-109.compute-1.amazonaws.com [05 Nov: 22:23:00] HEAD /dir1/file1.html
ec2-204-236-206-79.compute-1.amazonaws.com [05 Nov: 22:23:02] HEAD /dir1/file1.html
ec2-204-236-206-79.compute-1.amazonaws.com [05 Nov: 22:23:03] HEAD /dir1/file1.html
Oh, and PostRank almost always has a fellow amazonaws.com traveler, another HEAD hitter: "PycURL"
(Hits currently alternate versions: "PycURL/7.19.5" and "PycURL/7.18.2")
Seeing as how PostRank's (& PycURL's) benefits to me are nil, it remains just another blockworthy denizen of the cesspool that is AWS...
amazonaws.com plays host to wide variety of bad bots [webmasterworld.com]