Socks4/Socks5 Ranges

Afflicted · May 24, 2009

I have a good 20-30 SOCKS4/SOCKS5 1080 ranges.
Ex. format: 101.0.0.0 ~ 102.0.0.0
Each range USED to give anywhere from 25-100 legit, pretty much unique, ~24 hour Socks4 proxies. Is it possible these ranges still work?
I tried scanning one of them, and it seemed pretty dead. I still need to lvllord my computer for more TCP connections, or I might have a different problem going on from my ISP for proxy scanning. (Still on same OS as back in the day)
Anyone know if ranges go bad? These were from ~2004-2005 from the days I used to brute force.

Afflicted · May 25, 2009

proxy_go said:
afflicted i run 300 ip ranges for socks selling pm the ranges ille let u no
which are alive and dead .
but, i cant test the till monday, reason being is, alot of ip ranges yield
little socks on the weekend.

happy to check them if needed.

Ill check them myself, especially since they were hot back in the day. Could be valuable $$

It probably is just because its a weekend.

xmcp123 · May 25, 2009

From a few years ago (there are large dead ranges here, used to scan fast as hell)
60.0.0.0-69.255.25.255
80.0.0.0-89.255.255.255
24.0.0.0-24.255.255.255
12.0.0.0-12.255.255.255
200.0.0.0-201.255.255.255 <---there's gold in them thar IPs
I remember a bunch more in the 200s as well. A few DoD ranges though, so watch out.
When in doubt, Spamcop has a lovely map of the IPV4 space that is great for antis, as well as people looking to see the A class IP ranges that aren't heavily policed/are active. I can't post URLS yet, so pardon the lack of a link: spamcop.net/w3m?action=map

cheesecake · May 25, 2009

What kind of question is this? I don't get this thread at all.
First, are the socks legit? As in open and meant to be used as a socks? Are they a botnet? I'm guessing that you just found a list from 2005 that you used to use or even scanned yourself, well, 4 years is waaay too much time for a free/public socks or proxy server to live. Hopefully they'll last a week nowadays. Just get some new ones and see if they work and then you won't have to ask yourself if your ISP has something to do with it. And plus, ISP wouldn't matter since you are not the one with the port 1080 open. When you try to connect to port 1080, it doesn't go out port 1080 on your computer, but any other random port. So it makes no difference. Try connecting to one and do a netstat and check outgoing local port.
And to answer your question, people nowadays have built-in firewalls by default, routers and all sorts of stuff that people didn't use before.

cheesecake · May 25, 2009

xmcp123 said:
From a few years ago (there are large dead ranges here, used to scan fast as hell)
60.0.0.0-69.255.25.255
80.0.0.0-89.255.255.255
24.0.0.0-24.255.255.255
12.0.0.0-12.255.255.255
200.0.0.0-201.255.255.255 <---there's gold in them thar IPs

Highly unlikely. You are ruling out whole ISPs. My ISP for example falls under one of your "dead" A range. So how can be so sure that somebody on my ISP or myself even, doesn't have a socks server open to the public because it's misconfigured?

RandR · May 25, 2009

Wait, so the concept of this thread is to scan through ranges of IPs and hope to find an unprotected sock?
Basically brute forcing proxies...aren't there billions of possible combinations?
How many working socks would you be able to get using this method say, in 24 hours?

RandR · May 25, 2009

Doesn't that mean that mean that now there are fresh ranges (that I'm assuming most people don't know about) which will yield a decent amount of socks?

xmcp123 · May 25, 2009

cheesecake said:
Highly unlikely. You are ruling out whole ISPs. My ISP for example falls under one of your "dead" A range. So how can be so sure that somebody on my ISP or myself even, doesn't have a socks server open to the public because it's misconfigured?

I'm saying those are good ranges, but with large dead areas inside of them. For example, 80.0.0.0 (if I remember right) takes quite awhile to get going. So you may be pretty far into the range before you find some, but they are present. Sorry if I wasn't clear.
It's been years since I scanned, but I used to scan a LOT.

But no matter what you're going to be skipping IPs if you're scanning. A lot of areas just aren't worth the time. Like Level3 owns the entire 4.x.x.x a class, and there are proxies on it, but not enough to justify scanning the whole friggin a class.

Afflicted · May 25, 2009

proxy_go said:
socks ranges start at 0.0.0.0 going to 255.255.255.255

billions of combos and ports all yeilding socks
if u dont have the ports and the correct spots
in the range u could scan for socks for a lifetime
and get nothing.

trick is matching the port to th range
example i remember back in the day when
this range 203.115.64.0 - 203.115.96.0
got u 80 socks. range took less than 2 mins
to scan , but if u didnt no it was there ........ u get me

ranges from 2004-2005

61.1.0.0 - 61.1.255.255
61.11.70.0 - 61.11.130.255
61.17.160.0 - 61.17.255.255
61.144.50.0 - 61.144.54.255
60.254.0.0 - 61.254.70.0
66.155.120.0 - 66,155,130,0

now all crap all used up.

172.186.0.0 - 172.186.255.255
172.187.0.0 - 172.187.255.255
172.188.0.0 - 172.188.255.255
172.200.0.0 - 172.200.255.255
172.201.0.0 - 172.201.255.255
172.202.0.0 - 172.202.255.255
172.203.0.0 - 172.203.255.255
172.206.0.0 - 172.206.255.255
172.207.0.0 - 172.207.255.255
172.208.0.0 - 172.208.255.255
172.209.0.0 - 172.209.255.255
172.210.0.0 - 172.210.255.255
172.210.0.0 - 172.211.255.255
172.211.0.0 - 172.211.255.255

more crap these are ranges i use to
port back in early 04-05

190.30.0.0 - 190.30.255.255
190.48.0.0 - 190.48.255.255
190.49.0.0 - 190.49.255.255
190.50.130.0 - 190.50.185.255

these ranges back in 03-04 man u could get
5k socks from all these..now u be lucky to get
maybe 1-200..

201.0.0.0 - 201.0.255.255
201.1.0.0 - 201.1.255.255
201.12.172.0 - 201.12.196.0
201.13.0.0 - 201.13.130.0
201.19.0.0 - 201.255.255.255
201.22.0.0 - 201.22.255.255
201.25.95.0 - 201.25.255.255
201.26.0.0 - 201.26.255.255
201.27.0.0 - 201.27.255.255
201.29.0.0 - 201.29.255.255
201.42.0.0 - 201.42.255.255
201.43.0.0 - 201.43.255.255
201.48.0.0 - 201.48.255.255
201.68.0.0 - 201.68.255.255
201.80.0.0 - 201.80.255.255
201.92.0.0 - 201.92.255.255
201.95.0.0 - 201.95.190.0
201.128.1.1 - 201.129.255.255
201.135.1.1 - 201.138.255.255
201.144.1.1 - 201.145.255.255
201.154.0.0 - 201.154.255.255
201.208.0.0 - 201.208.255.255
201.236.200.0 - 201.236.255.255
201.250.0.0 - 201.250.255.255
201.252.0.0 - 201.252.255.255
201.254.0.0 - 201.254.255.255
201.255.0.0 - 201.255.255.255

in short 99% of all 2005 ranges dead rubbish
expired , garbage. end

Hahha there goes half my list of ranges.

I'm pretty sure I had more, these are just the ones I found a backup for.
61.1.0.0 61.2.0.0
61.17.0.0 61.18.0.0
172.177.0.0 172.180.0.0
172.187.0.0 172.188.0.0
172.200.0.0 172.204.0.0
172.206.0.0 172.209.0.0
172.210.0.0 172.216.0.0
200.72.0.0 200.73.0.0
200.78.0.0 200.79.0.0
200.84.0.0 200.85.0.0
200.90.0.0 200.91.0.0
200.93.0.0 200.94.0.0
200.106.0.0 200.107.0.0
200.114.0.0 200.145.0.0
200.118.0.0 200.119.0.0
200.120.0.0 200.122.0.0
200.122.0.0 200.123.0.0
200.161.0.0 200.162.0.0
200.233.0.0 200.234.0.0
201.11.0.0 201.17.0.0
201.20.0.0 201.23.0.0
201.133.0.0 201.134.0.0
201.144.0.0 201.145.0.0
201.20.0.0 201.21.0.0
201.153.0.0 201.155.0.0
201.128.0.0 201.130.0.0
201.137.0.0 201.138.0.0
201.250.0.0 201.251.0.0
201.252.0.0 201.253.0.0
201.254.0.0 202.0.0.0
203.5.0.0 203.6.0.0
203.17.0.0 203.18.0.0
203.29.0.0 203.30.0.0

HOT:
61.17.0.0 61.18.0.0
172.206.0.0 172.208.0.0
201.250.0.0 201.251.0.0
201.252.0.0 253.0.0.0
201.254.0.0 202.0.0.0
200.233.0.0 200.234.0.0
61.187.0.0 61.188.0.0
61.11.0.0 61.12.0.0

cheesecake · May 25, 2009

Sorry about this question but: Why does everyone refer to IP ranges from 2004-2005 ? Was that special socks year? It keeps coming up like if something special happened those years and I can't see why.
Seems like everybody has those years quite present in their minds like it was before and after free socks days. What was so special about it?

adonthenet · May 25, 2009

what do you use to scan?

Afflicted · May 26, 2009

proxy_go said:
me i scan for socks the old fashioned way
i port scan fresh socks

?time consuming? + less results? common ports only?

I used to scan ranges on 1080, 50033 (I think this was the port).

adonthenet said:
what do you use to scan?

I use pfinder, and TLS (Tiny little scanner, made for battle.net.) But still works 100% for checking lists, just gotta ignore the "bnet" and combine the export .txt files.
Pfinder is limited to ranges and port scanning, you cannot scan/check lists. Both programs together = all you need.
PM me if you want these.

RandR · May 26, 2009

How long did the scanning take for that list?

Socks4/Socks5 Ranges

Afflicted

Regular Member

Afflicted

Regular Member

xmcp123

Newbie

cheesecake

Regular Member

cheesecake

Regular Member

RandR

Registered Member

RandR

Registered Member

xmcp123

Newbie

Afflicted

Regular Member

cheesecake

Regular Member

adonthenet

Regular Member

Afflicted

Regular Member

RandR

Registered Member

Main Menu

Marketplace

Making Money

BlackHat World