[NPS] NiX Proxy Suite looking for testers and translators

Status
Not open for further replies.
Im now about done with Linux engine and I managed to give it just first test run. Checked 1k proxy using protocol auto-detect (one-pass check which does test everything at once; http (ssl connect), socks 4, socks 5 and socsk4/5 + socks proxies ssl connect and even SMTP).

1k proxy
100 threads
Operation completed in 36.3 seconds

During this weekend I'll be coding windows engine based on the new linux engine, im usually bad with ETA's but expect around 23th of May a new test version with proxy checker feature for both Linux/Windows.

PS. For Linux fans CLI version can be easily done as well but it will come after GUI version.
 
Advertise on BHW
It's worth the wait. Results below is a partial paste from 1k proxy check. This is another teaser.

Chunk: [0] completed in 1.67 seconds
Chunk: [1] completed in 1.65 seconds
Chunk: [2] completed in 1.69 seconds
Chunk: [3] completed in 1.73 seconds
Chunk: [4] completed in 1.59 seconds
Chunk: [5] completed in 1.72 seconds
Chunk: [6] completed in 1.81 seconds
Chunk: [7] completed in 2.14 seconds
Chunk: [8] completed in 1.91 seconds
Chunk: [9] completed in 2.23 seconds

Each 'chunk' is 100 connections per second and listed time after is what it took to determine should we test those proxy further. As you can read, NPS has extremely fast and reliable engine. This test was done on 10Mbps connection, currently I've no idea how much a slow connection such as 1-2Mbps can do. On my AMD 1090T (6x 3.2GHz cores), NPS consumes only 1-2% CPU from one core when using 100 threads.

Code: 
Chunk: [0] completed in 1.67 seconds 
connect() 98.21.97.18:6635 timed out
connect() 69.242.129.231:1420 timed out
connect() 66.7.126.183:183 timed out
connect() 71.195.70.219:1205 timed out
connect() 97.79.1.65:33161 timed out
connect() 96.252.83.246:1795 timed out
connect() 74.196.129.8:52501 timed out
connect() 203.188.230.4:1080 timed out
connect() 218.7.191.182:1080 OK
connect() 187.60.96.7:3128 OK
connect() 64.91.193.125:47799 timed out
connect() 67.81.13.128:1989 timed out
connect() 98.215.27.31:1283 timed out
connect() 72.220.5.116:27977 timed out
connect() 74.193.129.219:15958 timed out
connect() 74.142.173.85:35055 timed out
connect() 65.31.152.99:3459 timed out
connect() 24.96.242.243:1643 timed out
connect() 24.208.136.108:1432 timed out
connect() 71.199.104.43:48254 timed out
connect() 210.21.243.20:1080 timed out
connect() 76.73.130.43:1986 timed out
connect() 24.199.121.107:1393 [111] Connection refused
connect() 216.186.160.79:4859 timed out
connect() 216.219.43.43:42645 [111] Connection refused
connect() 184.161.119.207:6856 timed out
connect() 96.22.240.137:8818 timed out
connect() 24.252.78.146:9473 timed out
connect() 24.189.58.63:26715 timed out
connect() 76.164.199.167:14548 [111] Connection refused
connect() 68.44.110.121:29904 timed out
connect() 69.172.43.66:48480 timed out
connect() 209.203.193.6:27977 OK
connect() 98.201.29.211:1486 timed out
connect() 46.35.104.138:10298 timed out
connect() 74.102.83.112:52077 timed out
connect() 82.239.188.241:5999 timed out
connect() 96.238.7.203:1951 timed out
connect() 50.11.140.182:25739 timed out
connect() 173.44.95.28:1893 timed out
connect() 69.244.43.62:1967 timed out
connect() 174.107.154.210:23395 [111] Connection refused
connect() 75.149.86.17:48333 timed out
connect() 75.73.20.158:1457 timed out
connect() 70.177.116.66:1451 timed out
connect() 98.211.119.21:1795 timed out
connect() 98.217.76.59:1311 timed out
connect() 66.74.16.122:4681 timed out
connect() 200.127.28.168:6439 timed out
connect() 217.209.207.89:12429 timed out
connect() 98.119.57.101:61829 timed out
connect() 174.100.14.169:4838 timed out
connect() 66.134.58.235:14971 timed out
connect() 69.242.114.220:1881 timed out
connect() 217.26.14.18:3128 OK
connect() 24.49.168.72:17748 timed out
connect() 75.36.39.127:24699 [111] Connection refused
connect() 98.149.165.120:8649 timed out
connect() 71.245.69.176:2018 timed out
connect() 94.181.229.173:8609 timed out
connect() 67.186.62.91:6927 [111] Connection refused
connect() 69.142.86.34:13471 timed out
connect() 68.175.82.3:56439 timed out
connect() 24.99.188.10:1705 timed out
connect() 71.58.119.211:6097 [111] Connection refused
connect() 97.75.171.2:5551 timed out
connect() 67.81.13.128:53366 timed out
connect() 60.226.97.223:51263 timed out
connect() 98.204.109.104:20616 timed out
connect() 24.14.76.85:27977 timed out
connect() 72.47.91.250:1065 timed out
connect() 76.114.84.152:9851 timed out
connect() 180.153.103.114:1080 timed out
connect() 71.230.129.200:53795 timed out
connect() 72.186.116.115:6089 timed out
connect() 190.158.248.250:3128 OK
connect() 196.203.55.18:8080 timed out
connect() 71.56.42.130:1455 [111] Connection refused
connect() 98.219.61.77:1526 timed out
connect() 67.191.84.5:5849 timed out
connect() 188.233.122.63:8166 timed out
connect() 24.96.130.20:19345 timed out
connect() 77.121.230.23:6508 timed out
connect() 76.127.121.123:36869 [111] Connection refused
connect() 24.187.105.47:41366 timed out
connect() 75.111.7.160:48091 timed out
connect() 24.12.239.53:2342 timed out
connect() 24.46.243.223:33361 timed out
connect() 116.252.185.10:1080 timed out
connect() 8.24.248.21:1080 timed out
connect() 24.3.51.27:4007 timed out
connect() 142.169.118.250:7886 timed out
connect() 69.181.219.153:1333 timed out
connect() 69.254.210.184:42507 [111] Connection refused
connect() 122.205.95.14:80 timed out
connect() 24.127.204.167:1471 timed out
connect() 71.91.77.154:3311 timed out
connect() 65.188.39.252:1486 timed out
connect() 75.143.101.59:1108 timed out
connect() 68.49.239.232:27940 [111] Connection refused

Chunk: [1] completed in 1.65 seconds 

Background processess: 9
Array
(
    [connect_time] => 0.24
    [total_time] => 1.53
    [proxy] => 186.215.97.101:3128
    [proxy_type] => http
    [connect] => yes
    [anonylevel] => 3
)
Array
(
    [proxy] => 80.142.167.1:1080
    [proxy_type] => socks5
    [connect_time] => 0.06
    [total_time] => 0.36
    [proxy_dns] => yes
    [anonylevel] => 1
)


Operation completed in 44.98 seconds

On average using 100 threads, it takes only ~45 seconds to check 1k proxy, it does not matter are all proxies dead or alive, the speed will remain the same. Hourly checking speed will be approx. 80k proxy, it is about 2.5 times faster than the old NiX Proxy Checker PRO.

Windows version of NPS will not be as fast as the Linux version due to windows limitations, however it will still beat to death ANY other tool in terms of speed/reliability.

The listed results are almost comparable to native C/C++ program, considering that NPS is PHP based, the results are amazing. Im working over the clock to get windows version and GUI done.

PS. NPS will also have up-to-date IP Country/State/City information. There are various other unseen and advanced features coming but I'll speak about those features later. Needless to say, NPS will be the king of proxy leechers and checkers, so are ready for the new king? :)
 
wow thanks for the updated news and test results

and YES I AM READY for the new king :-)
 
if u ever consider more beta tester let me know bro thanks a lot
 
Last edited:
I'll check for more testers after the proxy checker has been implemented. I managed to finish windows proxy checker engine (it is different due to PHP's limited functionality on windows). I checked exactly the same 1k list on Linux and on Windows using XAMP. Here are the results:

100 threads and same timeouts

Linux: Operation completed in 53.77 seconds
Windows: Operation completed in 79.81 seconds

Please bear in mind that these checks had protocol auto-detection on, meaning all proxies will be tested for http, socks4, socks5 and socks4/5 + SSL CONNECT and SMTP checks! You will have the options to disable for example SSL/SMTP checks and you will also have the options to check only for http or socks proxies making the speed even faster.

We know windows engine was capable of checking 1k proxy in 80 seconds, it means on average 45k proxy per hour! Linux engine can check nearly 2 times more in an hour.

Currently linux version is anywhere between 40-50% faster. I am happy with the speed for both engines. Remember that I came up within a week with both engines ... it's not as easy to code as it may seem.

According to my current knowledge, NPS is the only tool in the world which has protocol auto-detection and monstrous checking speed compared to any other tool.

PS. I forgot to add that socks5 proxies will also be checked for socks5 feature 'Client cannot resolve the hostname', that feature is something that barely none else even ever hear about thus you haven't seen it yet in any other tool. With this feature you can just parse the proxies that are directly suitable for proxychains/proxifier where the proxy is cabable to resolve hostnames for you making for example your browsing even more stealth.

NPS will set the new standards when it comes for features, checking speed and reliability. Just for the comparison, checking 1k proxy with any other tool using the same amount of threads takes anywhere between 20-60minute and results are what they are ...

It's now just about coding the GUI and I can release the tool to the public worldwide. Prepare to flush toilets with your current tools.
 
I've some much ideas to use NPS's full potential, I've already codes for google PR checker with PR icon generation, I can modify it very easily into NPS as an extra. It is also possible to add scrapebox features into NPS, actually many other features as well. But first things first, let me finish the proxy checker and tester requested features in to the proxy leecher.

PS. I've coded also a year ago an advanced brute forcer which would also need a GUI. We may soon have 'NiX Security Suite' :P
 
Check the screenshot below. You'll have full control which types of proxies you want to test. Not all features has not been implemented yet. Before I can give the current release to the testers, I'll have to code real-time progress meter which will show estimated time remaining. I believe this is very important especially if you are testing very large lists ...

You should expect a release 24-25th of May.

Charon vs NPS

Settings:

- 100 threads
- Timeout 10 seconds
- Test for SOCKS 4,5 and 4/5

Proxies: 1k

Charon 7min 8 seconds
NPS Windows version: 1min 51 seconds
NPS Linux version: Operation completed in 32.36 seconds


NIX_PS.png
 
very nice ... looks promising

<real-time progress meter which will show estimated time remaining.>>
Yes i agree that's really a good idea
 
The release is delayed a bit due to my real life business, however it's almost ready to be released for current testers. A question:

Do you want a test version which don't have yet full database support for working proxies? Currently it writes working proxies to a text file.

Im actually done with windows GUI version but coding full database support with proxies search feature takes several days. Do you want to wait for those days or want to receive within a day the current version?

I worked hard and managed to implement exactly the same checking engine also for windows; read it's as reliable and almost as fast as the linux version! That means also windows version is capable of testing approx. 80k proxy/hour when using 100 threads and 100 sub-threads. So now also windows version can use sub-threads and retries setting works as well.

PS. What comes to win7 enterprise half-open connection limit's, it seems after all you don't have to lift the limit because when the proxy test was running, I verified via tcp-z for amout of half-open connections and the amount was equal to threads without patching it in kernel memory.

Another question: Would you like to have the option to define should the software include or remove for example gateway proxies? Like 'keep all' 'remove non-anon' fully automatically during the check?

Also real-time progress meter and estimated time remaining works good (it's always tricky to fix these features for a web app.)
 
i don't mind waiting for completed version
But you are referring to the windows version ?
How is the linux test version ? completed ?
 
I was referring to windows version. However it takes only a few hours to finish linux GUI version. Im almost done as well for linux CLI version. I started coding this tool with linux version so there is not that much work left for the CLI version.

Do you want the linux CLI version this way:

nps_cli.php timeout=2 and so on. I was thinking about coding it in the way where you set it's setting via GUI and just run it with only few parameters, if i add all features on command line, it will easily have 20+ options ... There are various features coming that was not listed in the previous screenshot ...

PS. Linux CLI version will definitely be the most powerful version in terms of speed, reliability and memory/cpu usage. I am not saying windows version is bad, it will easily beat any other tool, that's what I know for sure.

I haven't had yet time to test but I believe if you have a good dedicated server or a powerful VPS on a good connection, I believe you can easily check with 200-400 threads which will allow you to check millions of proxies per day ... however I absolutely take no responsibility if your server gets suspended :) I quickly counted that approx. 80k per hour == 1,9 million per day when using 100/100 threads
 
Here's a video of NPS Linux CLI version: http://myproxylists.com/NPS_Linux_CLI.mp4

I checked 1k proxy using 100/100 threads and protocol-audetection (check the arrays, you will notice it detects all types of proxies exactly as promised earlier). What is missing is IP-COUNTRY + add proxies on the fly to the database, that means using the GUI version while the CLI version is testing proxies, any working proxy is instantly available. That is exactly how the upcoming automation will work. For example you just automate proxy leeching process and just after it finished the proxy test will start. This is how I've had it for over a year using my current tools.

I hope this video backup's all my claims so far about speed/reliablity and about NPS being the new king of proxy leechers/checkers ;). Windows GUI version uses the same engine and is almost as good expect it takes a lot more ram compared to CLI.

PS. Watch the video carefully, there's a progress meter as well and it is very accurate about estimated time remaining.
 
<<<was thinking about coding it in the way where you set it's setting via GUI and just run it with only few parameters, if i add all features on command line, it will easily have 20+ options >>>
==> yeah that would be nice to set the settings via GUI .. easier for everybody rather than edit .php files each time BUT it is up to you of course.

Really looks powerful ..i had many proxy tools in my pocket these past years, i am looking forward to see it completed and tested ...

<<automate proxy leeching process and just after it finished the proxy test will start.>>
==> that's really what we need . automate process ..

When we finished testing it, etc .. whats your plan about selling it ? price etc
 
Last edited:
I assume you're interested in Linux CLI version? Let me know asap. I'll work today and sent you tonight a new test version. If you have a VPS or dedicated server, it needs to be tested on a fast connection. It actually needs to be tested also on a slow connection, i am curious to see will NPS kill someone's connection, 100 threads is quite massive for a home connection.

You remember from proxy leecher those process ID's that it generates randomly upon a new test. For the CLI I'll do it this way: nps_cli.php username processId (it will then grab that leeched list accordingly from the database and does checking and will of course also write all working proxies to the proxies database with the same username and ID).

This way you can view real-time results of your current CLI proxycheck also via the GUI and don't need necessarily wait for whole check to finish. This is the way my system does it, so user's gets all working proxy instantly, this way you can check massive lists without worrying proxies dying during the check.

PS. As you said, I've been in proxy's since 2007 and nothing changed, due to current tools, we see a ton of copy/pasted and untested trash. Why? Simply because current tools are either too slow or unreliable to test big lists. Im here to fix this issue with the free version of NPS.

I've to say I haven't thought of pricing. My plan is to release reasonably good free version but I'll need to also release commericial version because I need to get something out of this massive work.
 
yes interested in the linux GUI version of it for now.
but maybe also your windows version too in the future .. i will see when you are done and have your prices ready

<<his is the way my system does it, so user's gets all working proxy instantly, this way you can check massive lists without worrying proxies dying during the check.>>
==> thats really great

Thanks for the updates
 
I would like to test the completed windows version and don't mind waiting a few days to test the same.
 
I will send you soon windows version with the proxy checker feature, im almost done by now with Linux/Windows GUI versions. There are that many features coming that if I complete them all, it will take weeks. Therefore I would like that you guys test the proxy checker feature as soon as possible.

I will be working all the time with features as I need those features myself as well, I can't wait to get this new tool replacing my current tools/automation as it is so much more powerful.

Expect anywhere between 1-3 days a new version. I'll sent you guys PM when it's available.
 
I've sent PM's to current few testers and im awaiting for your feedback. Remember to test also big lists such as 10-100k if possible. My ISP is very bitchy and therefore I never tested larger than 1k lists.

Please test all protocols and whenever you see a new proxy appearing to 'proxies.txt', remember to verify it via browser. I've put a lot of my time to engine reliability and there should not be any change that a fake proxy would appear in the results but you never know.

I would like to also hear about checking speed with threads X and sub-threads and most importantly about overal speed/reliability. I'll keep one day break and I'll then add previously requested features to the proxy leecher. Needless to say, the proxy checker will also have the option to check custom lists but this feature did not made into the version I just sent you.
 
i forgot to answer that question "Another question: Would you like to have the option to define should the software include or remove for example gateway proxies? Like 'keep all' 'remove non-anon' fully automatically during the check?" just saw it now re reading the posts .. sorry

Yes would be nice to be able to tell the script to Keep all, remove non-ann etc ...
 
Advertise on BHW
Status
Not open for further replies.
Sign up now!

Main Menu

Home Main Forum List Black Hat SEO White Hat SEO BHW Newbie Guide Blogging Black Hat Tools Social Media Downloads

Marketplace

Account Selling Content / Copywriting EBooks / Methods Hosting Misc Proxies For Sale SEO - Link building SEO - Packages Social Media Social Media - Panels Web Design More

Making Money

Affiliate Programs Hire a Freelancer IM Journeys Making Money Pay Per Click Site Flipping Want to Buy

BlackHat World

Dispute Resolution Forum Suggestions & Feedback Introductions Lounge
Back
Top