|
Author: P.Hauser (6 Mar 08 5:38am)
ec2-67-202-34-117.compute-1.amazonaws.com reverse looks up to an IP 67.202.34.117. So you would have to check this IP. The IP belongs to a customer of the "Amazon Elastic Compute Cloud", which is an AMAZON webservice API.
Information about this AMAZON API and how to use it, can be found at http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/
General Information about this AMAZON webservice can be found at http://www.amazon.com/gp/browse.html?node=201590011
Most of the crawlers that come from this range are datamining crawlers of AMAZON customers. So it is important to understand that there is NOT AMAZON crawling, but more or less legitimite customers, who pay for that webservice.
Examples, what can be done from the customers with this webservice are e.g. here:
http://www.datawrangling.com/
../on-demand-mpi-cluster-with-python-and-ec2-part-1-of-3.html
http://www.datawrangling.com/
../mpi-cluster-with-python-and-amazon-ec2-part-2-of-3.html
another one is http://www.page-store.com/ who uses it for crawling with a user agent "Mozilla/5.0 (compatible; heritrix/1.12.1 +http://www.page-store.com) [email:paul@page-store.com]" at IP 72.44.49.137 or DNS ec2-72-44-49-137.z-1.compute-1.amazonaws.com
The source http://jtv.itsmycrap.com/forum/showthread.php?p=358 shows that some AMAZON-IPs are even used as IRC-servers.
So you would have to decide individually, if you have a good or a bad AMAZON datamining customer. IP 67.202.34.117 seems to have a crawler with a Russian or Ukrainian datamining background. You can find it here and add your comment.
Hope that helps you out.
Post Edited (7 Mar 08 5:55am)
|
Welcome to Project Honey Pot | Login