[GET] Google Proxy Checker (Built for BHW)
- Thread starter kokoloko75
- Start date
Great tool, thanks for the share.
I would like to suggest an additional feature, if you are likely to upgrade it in the future. It would be great if the time that is reported on the screen could also be saved to the valid file. This would mean that you could then easily sort the file in a spreadsheet if you wanted to use only the fastest proxies.
I would like to suggest an additional feature, if you are likely to upgrade it in the future. It would be great if the time that is reported on the screen could also be saved to the valid file. This would mean that you could then easily sort the file in a spreadsheet if you wanted to use only the fastest proxies.
hasrulhere
Newbie
- Apr 24, 2013
- 6
- 0
Tq... very use fulll... 
eace:
eace:Good idea, but it has a few problems. I dumped 204,000 raw proxies of all types (Elite, anonymous, transparent, Google enabled, not G enabled, sock 4 & 5), 5700 known to be good. 589 that would work in the scraper that I use. The checker promptly choked. It took quite a while to load the proxies - far longer than it would to download them from the program I use. I set the threads to 100 and the timeout to 60 and launched.
Here are the first few entries from the valid file:
:3128
:443
:80
:8080
:8118
Notice that the entries are only the ports. After those bad entries from properly formatted IPort entries, the program began to work but only picked up 43 good, of a known 5700 good, proxies. After checking 1838 proxies, the program seized. The program on a large proxy set also read the wrong number of proxies (44000 when 204000 were loaded). I rebooted the computer three times and reran the test. Same result each time. On a much smaller set of filtered proxies, the program appeared to work properly.
Here are the first few entries from the valid file:
:3128
:443
:80
:8080
:8118
Notice that the entries are only the ports. After those bad entries from properly formatted IP
ort entries, the program began to work but only picked up 43 good, of a known 5700 good, proxies. After checking 1838 proxies, the program seized. The program on a large proxy set also read the wrong number of proxies (44000 when 204000 were loaded). I rebooted the computer three times and reran the test. Same result each time. On a much smaller set of filtered proxies, the program appeared to work properly.
Last edited:
cody41
Power Member
- Jun 18, 2009
- 691
- 276
Good feedback. What other tools are you using just to filter/verify google passed proxies?
Good idea, but it has a few problems. I dumped 204,000 raw proxies of all types (Elite, anonymous, transparent, Google enabled, not G enabled, sock 4 & 5), 5700 known to be good. 589 that would work in the scraper that I use. The checker promptly choked. It took quite a while to load the proxies - far longer than it would to download them from the program I use. I set the threads to 100 and the timeout to 60 and launched.
Here are the first few entries from the valid file:
:3128
:443
:80
:8080
:8118
Notice that the entries are only the ports. After those bad entries from properly formatted IP
Awesome tool. It's fast, checks many at once, and it tests for the useful of whether the proxy can connect to an actual site, and what manner of page google brings up, it's the best tool of any i've found. Plus, the UI is extremely easy on the eyes
Unfortunately, it seems like google changed something cuz lately most of a list will be displayed as invalid, but I can connect to google through them in my ordinary web browser.
Unfortunately, it seems like google changed something cuz lately most of a list will be displayed as invalid, but I can connect to google through them in my ordinary web browser.
snowcouples
Newbie
- Dec 29, 2012
- 4
- 0
thanks for the share now for the harvester
There is no such thing as "optimal settings". It all depends of internet connection and hardware.
seosuperman1
Regular Member
- May 25, 2010
- 340
- 77