FREE TOOL · UP TO 100 PROXIES PER RUN
Batch proxy checker
Paste your whole proxy list and test every entry in one go. Each proxy gets its own verdict: live or dead, which protocol answered, the exit IP, and how fast it responded.
BATCH TEST BENCH
0 / 100
One proxy per line, up to 100. Lines that name their own protocol, like socks5://, keep it. Everything else uses the dropdown.
01
What this tool does
Proxy lists rot. Providers rotate ranges, free lists fill with dead servers, and the pool you set up last month quietly loses a few proxies every week. Checking them one at a time is miserable, so this page takes the whole list at once.
Paste up to 100 proxies, one per line, and hit check. The tool runs several tests in parallel and fills in results as they land. Every line gets one real request through the proxy, the same test the single proxy checker runs, so a green result here means the proxy actually moved traffic, not just that the port was open.
02
How to check a proxy list
- 01Paste your list, one proxy per line. Mixed lists are fine: lines that name their own protocol, like socks5://host:port, keep it, and every other line uses the dropdown.
- 02Leave the protocol on Auto unless you know better. Auto tries HTTP, SOCKS5 and SOCKS4 against each proxy and records whichever one answered.
- 03Hit check and watch the report fill in. When the run finishes, one click copies all the live proxies, ready to paste into whatever you are building.
ACCEPTED FORMATS
protocol://username:password@host:port
protocol://host:port
host:port (protocol taken from the dropdown)
Duplicate lines are removed automatically, so you can paste straight from a messy file without cleaning it up first.
03
Reading the batch report
Each row shows the proxy you entered, the protocol that worked, the exit IP, and the response time. Failed rows show the exact error instead, and the counter at the top keeps a running tally of live and dead.
Two things to keep in mind before you delete the failures. First, a proxy that fails here but works on your machine usually means IP allowlisting: your provider accepts connections from your registered IP and refuses our test server. Second, overloaded proxies sometimes time out on the first attempt and pass on the second, so a retest of the failures is worth ten seconds before you throw them away. The full decoder for every error message is in common proxy errors and how to fix them.
04
Where a batch check fits
The obvious moment is right after buying: run the fresh list through, confirm the advertised countries match the report, and open a support ticket while the purchase is still new if half of them are dead. The less obvious moment is before every serious scraping run. Pruning dead proxies from your pool up front costs a minute and saves you from debugging mystery failures in your own logs later.
One honest limit: this tool tells you a proxy works and where it exits. It cannot tell you whether your target website will accept that proxy, because working and welcome are different things. If your live proxies still get blocked somewhere, residential vs datacenter proxies explains what the site is seeing.
05
Frequently asked questions
Is the batch proxy checker free?
Yes. Same deal as the single checker: no account, no trial, no credit card. Paste your list and go.
How many proxies can I test at once?
Up to 100 per run. The cap keeps the tool fast and free for everyone. If your list is longer, split it and run it in chunks; each run takes well under a minute for most lists.
Can I mix HTTP and SOCKS proxies in one list?
Yes. Leave the protocol dropdown on Auto and each proxy is tested against HTTP, SOCKS5 and SOCKS4, with the working protocol shown in its row. Lines that include their own scheme, like socks5://host:port, are always tested as written.
What format does the list need?
One proxy per line, in any of the usual shapes: host:port, user:pass@host:port, or a full URL like http://user:pass@host:port. Duplicates are removed automatically.
Do you store the proxy lists people paste here?
No. Each proxy is used for one test request and nothing is written to a database. Lists are not collected, kept, or shared.
Related: How the checker works
Why did my entire list fail?
When every single line fails the same way, the proxies are usually fine and the access is not. Most often the provider allowlists your IP address, and our test server is not on that list. Test from your own machine with curl, or switch the proxies to username and password authentication and run the batch again.
Can I export the working proxies?
Yes. When the run finishes, a copy button appears under the report. It copies every live proxy to your clipboard, one per line, with the detected protocol included so the list is ready to use.
06
More checkers
07
From the blog
How to test if a proxy is working (3 reliable ways)
Common proxy errors and how to fix them
Residential vs datacenter proxies: an honest comparison