Re: Re: can scan, but not test

Paul Howarth <[email protected]> Tue, 12 Apr 2005 17:09:48 +0100
Newsgroups gmane.mail.spam.dsbl.general
Message-ID <[email protected]>
Dick Wesseling wrote:
> I am still having trouble with proxies that can be scanned but not 
> tested. To refresh your memory, here is what I wrote in october:
> 
> 
>>I noticed an interesting phenomenon that I am unable to explain,
>>maybe this is familiar to some of you. The phenomenon is that I can
>>portscan certain proxies (all of the same spam gang) but I cannot
>>test them. That is, my scanner send a syn and receives ack+syn, but
>>when using proxycheck on that port, the packet flow is  s:syn,
>>r:ack+syn, s:data, r:RST. This happens with several hosts on my /27.
> 
> 
>>The interesting thing is that if I run proxycheck from a couple of
>>hosts on another network it always works....
> 
> 
> Could you guys do me a favor and run the following list through 
> proxycheck and let me know how many open proxies it reports? I expect 
> either +- 20-30 or 0.

None here:
$ pxtest -v -p s4:10099 `cat proxies`
To check: hosts=45, proto:ports=1, host:proto:ports=45
213.35.250.108:s4:10099: Connection reset by peer
194.158.77.163:s4:10099: EOF
80.118.241.190:s4:10099: EOF
84.99.33.47:s4:10099: EOF
217.97.70.16:s4:10099: EOF
82.255.51.53:s4:10099: EOF
195.23.251.38:s4:10099: EOF
162.40.24.187:s4:10099: EOF
81.218.50.241:s4:10099: EOF
68.239.133.251:s4:10099: EOF
85.64.115.75:s4:10099: Connection reset by peer
82.55.129.41:s4:10099: EOF
83.196.194.94:s4:10099: EOF
67.10.242.205:s4:10099: EOF
81.192.196.100:s4:10099: EOF
83.130.164.22:s4:10099: Connection reset by peer
69.3.130.85:s4:10099: EOF
83.102.235.80:s4:10099: Connection reset by peer
60.49.47.163:s4:10099: EOF
201.254.35.105:s4:10099: Connection reset by peer
60.48.194.252:s4:10099: EOF
201.8.186.230:s4:10099: EOF
68.234.156.205:s4:10099: EOF
66.50.29.161:s4:10099: Connection reset by peer
85.97.51.118:s4:10099: Connection reset by peer
217.132.33.239:s4:10099: Connection reset by peer
70.216.183.120:s4:10099: Connection timed out
NumOpen=0(0) NRead=0 Time=30

These appear to be very common unfortunately.

Paul.

----------------------------------------------
This message was sent to the opt-in DSBL list.
If you do not want to receive DSBL messages,
please send mail to [email protected].