AWS views proxy checking as an abusive activity

[rdavydov]

Information for consideration

• Reported Activity: Port Scanning
• Activity which resembles attempts to access remote hosts on the internet without authorization. This incident was generated when a malicious party connected to a honeypot service.

AWS has automatically taken action due to no response from the client:

• Blocked outbound TCP ports 3128, 3127
• Blocked outbound TCP port: 8080

[rdavydov]

** FINAL NOTIFICATION **

Hello,

We have not received a response regarding the abuse report implicating resources on your account. To mitigate the abuse, we have taken the following steps:

***Blocked all traffic, allowing administrative access only***

Reported Activity: Intrusion Attempts

The reported activity listed below violates the AWS Acceptable Use Policy (https://aws.amazon.com/aup/ ). In order to resolve this report please reply to this email with the corrective action taken to cease the activity.

Required Actions: Investigate root cause

If you require further assistance with resolving this abuse report/complaint please see: https://aws.amazon.com/premiumsupport/knowledge-center/aws-abuse-report/

If you do not consider the activity abusive, please reply to this email detailing the reasons why.

Regards,
AWS Trust & Safety

It's not safe to run proxy checking with AWS. They blocked all traffic, had to terminate the instance.

[watchingdogs]

How much bandwidth did it take per month to run the checker?

[rdavydov]

How much bandwidth did it take per month to run the checker?

Never measured.

[watchingdogs]

If not, then can you tell about how the code worked or even share it? Did you request some IP tracking website for all addresses through the proxy connections?

[watchingdogs]

Also even if you can't find a free server, there are some pretty cheap ones available out there.
https://www.serverhunter.com/

[rdavydov]

If not, then can you tell about how the code worked or even share it? Did you request some IP tracking website for all addresses through the proxy connections?

the code is in the repo, .sh files

[watchingdogs]

Where's start.sh and main.py?

[rdavydov]

Where's start.sh and main.py?

I'm afraid it is not for you if you can't even figure this out.

Hint: cd ~/proxy-scraper-checker

[watchingdogs]

I just didn't bother to do it.
However, now I've found the repos monosans hosts, both the proxy checker and also a similar proxy list.
I don't see why you selfhosted the checker repository if you could have just used the original in the first place.
Again, if you intend to keep hosting it, I can recommend the VPS comparison site I linked.

[rdavydov]

I don't see why you selfhosted the checker repository

I didn't. You're misrepresenting the facts.

I made this proxy-list for my own personal usage when their repo was down.

I just didn't bother to do it.

This conversation is over then. I don't see the point in your messages.