4 ms·
It was based on IP address. You're right in that all hosting services suffer this problem to some degree, but it's a particular problem on EC2 since it's so ea
by dpapathanasiou 17y ago
It was based on IP address.
You're right in that all hosting services suffer this problem to some degree, but it's a particular problem on EC2 since it's so easy to request IP for an instance that does something bad, then release back into the pool for other instances to use, a short time later.
It only costs a few dollars to that on EC2, whereas most other hosting services require at least a month's commitment and higher fee(s) before you can defile one of their IP addresses.
BTW, the reason I posted was to find out what other blacklists might be out there, so if your company is blocking access, I'd appreciate letting me know which service they're using.
- talison 17y agoAre you sure it was based on IP address? This domain was used to host questionable links a few years ago, including suspicious antivirus software: http://web.archive.org/web/*/workstax.com http://web.archive.org/web/*/workstax.com http://web.archive.org/web/20070127212047/http://workstax.com/ http://web.archive.org/web/20070127212047/http://workstax.co...
- dpapathanasiou 17y agoYou're right about the prior activity for the domain, but both Blue Coat and McAfee complained based on the IP address we're using now (i.e., the EC2 address). But my purpose in posting this is to ask: what other filtering lists are out there? Getting ourselves off is easy now, since we are a legitimate site; the hard part is figuring out who else may be blocking us.