(Announcement): I am planning on releasing V1.3/V2.0 fairly soon, so if you have any thoughts on features feel free to send them to me or post them here
The current latest and most feature-rich version is 1.2, although you are free to use version 1.1 if you don't need the new features.
So, currently there are two ways to check proxies:
- Check a specific proxy (IP:PORT)
- Check a big list of proxies simultaneously (multi-threaded approach)
Before you start using the code, you will have to grab a copy of the latest release, available here. Also note that this documentation is only related to the latest release, for other docs visit our page
Locate the checker.php script, and GET it with the parameters ip, port and timeout:
checker.php?ip=137.116.76.252&port=3128&timeout=20
This code will check the proxy 137.116.76.252:3128 with a timeout of 20 seconds.
Results are returned in JSON format:
{
"result": {
"success": true,
"proxy": {
"ip": "137.116.76.252",
"port": "3128",
"speed": 339
}
}
}And in the case of faliure you will get the reason why it failed (curl_error direct return):
{
"result":{
"success":false,
"error":"Operation timed out after 1000 milliseconds with 0 bytes received",
"proxy":{
"ip":"186.227.185.123",
"port":"80"
}
}
}If you are using version 1.2 you will also be able to check SOCKS4/5 proxies. In version 1.2 the proxy is checked for SOCKS by default after it has partially failed a check for HTTP (Connection reset error), however knowing for sure whether it is a SOCKS proxy you are about to check or no can minimise the time it will take to process.
To check the proxy for SOCKS only use the proxy_type GET parameter:
localhost/checker.php?ip=201.173.168.52&port=10000&timeout=20&proxy_type=socks
Unless the list of proxies you want to check is really small, you'll want to use multi-threading which can speed up requests exponentially.
This feature works best if you supply a file with a list of proxies in it (Most free proxy listing websites will allow you to export proxies in IP:PORT format).
To check a list of proxies contained in file abc.txt with a timeout of 20 seconds:
localhost/checker.php?file=abc.txt&timeout=20
This uses multi-threading and hence instead of taking 200 seconds for 10 proxies (20 secs timeout * 10 proxies), it will take roughly 30 seconds to finish.
However, the results are going to be a bit different this time, because you've checked a big list of proxies instead of one:
{
"results":[
{
"success":true,
"proxy":{
"ip":"186.227.185.123",
"port":"80",
"speed":2300
}
},
{
"success":true,
"proxy":{
"ip":"186.227.56.162",
"port":"80",
"speed":623
}
},
{
"success":true,
"proxy":{
"ip":"221.212.74.203",
"port":"63163",
"speed":907
}
},
{
"success":true,
"proxy":{
"ip":"180.166.112.47",
"port":"8888",
"speed":1468
}
},
{
"success":true,
"proxy":{
"ip":"221.212.74.203",
"port":"12",
"speed":802
}
},
{
"success":true,
"proxy":{
"ip":"221.212.74.204",
"port":"12",
"speed":779
}
},
{
"success":true,
"proxy":{
"ip":"221.212.74.204",
"port":"19452",
"speed":803
}
},
{
"success":true,
"proxy":{
"ip":"219.237.16.38",
"port":"80",
"speed":12909
}
},
{
"success":true,
"proxy":{
"ip":"221.212.74.204",
"port":"933",
"speed":874
}
},
{
"success":true,
"proxy":{
"ip":"131.0.168.86",
"port":"80",
"speed":8802
}
}
]
} As you can see from the json, it has an array of 'results' with results for each and every proxy in the list.
See note above about SOCKS proxy support.
Same principal applies to big lists (multi-threaded checking).
Version 1.3 (Estimated release date : Unknown)
- Will have a version supporting includes (as a library)
- Finally adding proxy annonimity tests
- Adding multi-threading without the need for file includes (GET arrays)
- Possibly support for other file formats
Version 1.2 NEW (Fixes & Updates to Version 1.1)
- Now supporting SOCKS4/5 proxies!
- Added proxy type field in outputted JSON
- All proxy checking scripts have been updated, and some bugs have been fixed
Version 1.1 (Updated from Version 1.0)
- Dropped command-line support, now using a browser-approach (GET Requests)
- Switched to stable and working methods (100% accurate proxy checks)
- Increased speed and multi-threading ability
- Added support for checking single proxies individually
- You can now specify a custom
timeout
| Version number | Working | Bug Rating | Documentation |
|---|---|---|---|
| Version 1.2 | Yes | Stable | V1.2 Release |
| Version 1.1 | Yes | Stable | V1.1 Branch |
| Version 1.0 | N/A | No Support | V1.0 Outdated |
- Sometimes regards dead HTTP(S) proxies as SOCKS4/5 proxies
- Can't handle SOCKS proxies (Returns operation timed out error) Fixed in 1.2
Me (Samuel Allan) for creating and maintaining the code.
W. Al Maawali for the script that V1.1 was built on.
Miyachung for creating the script that V1.0 was wrapped around.
You can contact me (Samuel Allan) at [email protected] or [email protected]
W. Al Maawali - Link to the script that made V1.1 possible
You can contact Miyachung at [email protected]