Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Please make a way to authenticate incoming pinterest EC2 requests from the web vs other garbage traffic from EC2.

Or just simply publish your outgoing EC2 ip pool list.

We cannot completely block EC2 because of Pinterest and that's a bad situation.



Why do you need to block EC2?


Because it is a source of some very bad traffic. Anybody doing web-facing stuff that is targeted by bots/jerks/spammers/all of the above will block hosting facilities wholesale.


I am interested in doing this. Do you have any information on how to find out which IP ranges belong to server hosts? I couldn't find any useful results searching google.


here are a few lists to get you started:

http://proxy-ip-list.com/download/proxy-list-port-3128.txt http://proxy-ip-list.com/download/free-usa-proxy-ip.txt http://www.proxylists.net/http_highanon.txt http://www.proxylists.net/socks4.txt http://www.proxylists.net/socks5.txt http://www.stopforumspam.com/downloads/listed_ip_90.zip

I've got my own db of hosting facilities which I made by taking 100M urls and doing a lookup on the hostname, then saving the IP found in a db. This gives you some level of confidence that a certain class 'C' is used for hosting.


It's also possible to build such a list by watching for static ips that do more than "x" requests and queuing rdns on them.

Google is easy to identify this way, even with a spoofed user agent (which they do a lot now).

But this technique is not possible with EC2 because Amazon refuses to make a public database of what customer is using what.


> Google is easy to identify this way, even with a spoofed user agent (which they do a lot now).

That's part of their page-cloaking detection code.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: