Free tool
Free proxy checkerfor HTTP, SOCKS4 and SOCKS5
Paste or drop any list and test every proxy against a live connection. You get status, speed, anonymity, country and network back per line, streaming in as each one answers. Up to 100,000 proxies per run, with no account, no install and no cap on how many lists you check.
Your list
Empty runs the sample listEvery common format works, mixed freely.
Load from a file
Drop your proxy files here
.txt or .csv, as many as you like. Every line lands in your list.
Probe settings
Protocols to probe
Per proxy
What you get backfor every line you paste
Most free checkers answer one question, up or down. This one returns the whole profile, because whether a proxy is alive is rarely what decides if it will work for your job.
Status
Working, dead, or timed out, decided by opening a real connection through the proxy right now. Nothing here comes from a stored list that was true last week.
Protocol
HTTP, HTTPS, SOCKS4 or SOCKS5, detected from the handshake rather than from the port number, so a SOCKS5 proxy sitting on 8080 is still identified correctly.
Anonymity
Elite, anonymous or transparent, read from the headers the proxy actually forwards. This is the field that tells you whether it is leaking your real IP.
Location
Country and city, with a flag, resolved from the exit IP. You get this even for proxies that failed, because knowing where a dead endpoint lives is still worth something.
Network
The ISP and the autonomous system number behind the IP, plus whether that ASN is a datacenter range or a residential one. That single distinction predicts most blocks.
Speed
Round-trip latency in milliseconds, sampled more than once so a single slow handshake does not misrepresent an otherwise fast proxy.
Reading the results
Your list came back.What each verdict is worth.
A status is the first half of an answer, not the whole one. The same word means different things depending on the network behind the address and the wait you allowed, and that difference is what decides whether a proxy that tests green survives its first real request.
- Working, Elite
- The proxy answered and forwarded nothing that gives you away. No X-Forwarded-For, no Via, no proxy headers at all, so the target sees an ordinary visitor arriving from the proxy's own address.
- This is the one you keep. Copy the working set out now, because a verdict is only true for the moment it was taken.
- Working, Anonymous
- Your address is not forwarded, so you are not identified, but the request still carries a header announcing that a proxy is in the path.
- Fine for ordinary pages. Expect challenges on targets that treat the admission itself as a reason to look harder at you.
- Working, Transparent
- The proxy forwarded your real IP in a header. It works, and it hides nothing.
- Filter these out of anything privacy related. They are only useful as plain caches.
- Working, datacenter network
- The connection is healthy and the ASN behind it belongs to a hosting provider. Consumer sites score whole hosting ranges long before they look at your individual request.
- Read the Network column, not just the status. When a target keeps blocking you while every proxy tests green, this is almost always the reason.
- Working, slow
- Alive, and far away or overloaded. The number is a full round trip through the proxy, sampled more than once so a single bad handshake does not decide it.
- Anything past a second will hurt once you run work in parallel. Sort by latency and keep the top of the list.
- Timeout
- Nothing came back inside the wait you allowed. That is a statement about your wait as much as about the proxy.
- Raise Wait per proxy, turn on a retry, and run the failures again before deleting them. A proxy on the other side of the world is not dead, it is far away.
- Dead
- The connection was refused or reset, or the handshake never finished. The endpoint is closed, gone, or was never really open.
- Nothing to salvage. If a run of dead rows shares one name in the Network column, that whole range is gone and the rest of that source is not worth testing.
Input
Every format it accepts,mixed in one paste
You should not have to normalise a list before you can test it. Paste whatever your source gave you, in whatever combination, and each line is parsed on its own.
Line formats
host:port
The plain form. 192.241.113.20:8080
host:port:user:pass
Credentials appended. 45.79.12.44:3128:user:pass
user:pass@host:port
Credentials in front. user:pass@138.68.60.8:1080
scheme://host:port
With the scheme spelled out. socks5://51.158.68.133:8811
Protocols
HTTP
The plain web proxy. Fine for scraping ordinary pages, and the easiest kind for a site to spot.
HTTPS
An HTTP proxy that will open an encrypted tunnel with CONNECT, so your traffic stays private from the proxy operator.
SOCKS4
A lower-level tunnel. It carries any TCP traffic, not just web requests, but it cannot do authentication or IPv6.
SOCKS5
The one most people want. Any TCP traffic, username and password auth, IPv6, and remote DNS so your lookups do not leak.
Anonymity
Elite, anonymous, transparent,and why it decides everything
This is the field people skip, and then wonder why a proxy that connects perfectly still got them blocked on the first request. All three of these work. Only one of them keeps your address to itself.
Elite
High anonymous
The proxy sends nothing that gives you away. No X-Forwarded-For, no Via, no proxy headers at all. The site sees an ordinary visitor coming from the proxy's own IP and has no header-level reason to think otherwise.
Anonymous
Hides you, announces itself
Your real IP is not forwarded, so you are not identified, but the request carries a header that says a proxy is involved. Plenty of sites treat that admission alone as a reason to challenge the request.
Transparent
Leaks your real IP
The proxy forwards your original address in a header. The site can read it, so you get none of the privacy you were after. Useful for caching, useless for anonymity.
The honest part
Why a list that worked yesterdayis dead this morning
Nobody enjoys re-checking the same file every day, so it is worth knowing what actually kills a proxy. Three of the four reasons below have nothing to do with the proxy going offline.
The IP got burned
Free proxies are shared by definition. Every person hammering the same endpoint into the same target teaches that target to block the range, and once an ASN is flagged the whole block goes with it. This is why a proxy can answer in 80ms and still fail every request you care about.
The host took it down
A large share of public proxies are misconfigured servers that were never meant to be open in the first place. The moment somebody notices the bill or the traffic, it closes. There is nobody to complain to, because it was never a service.
It was never really alive
Some endpoints accept a connection and then quietly drop or rewrite the traffic. They pass a naive ping and fail a real request, which is exactly why this checker completes a genuine handshake per protocol instead of just probing whether the port is open.
The rotation moved on
Rotating pools recycle addresses constantly. An IP that answered an hour ago may now belong to a different customer, a different city, or nobody at all. A list is a snapshot, and the only honest way to use one is to re-check it before every job.
Why a checker
this good is free
100,000
Proxies per run, no account
HProxy runs a live proxy network, which means verifying proxies at scale is something our infrastructure already does every second of every day. Handing that same engine to everyone costs us very little and it keeps the whole community working off cleaner lists.
There is no upsell wall and no teaser. You see every result, you can export all of them, and nothing asks you to pay to unlock a column. When you get tired of re-checking free lists every morning, our residential, ISP, datacenter and mobile pools are one click away, and that is the only pitch.
Nothing to test yet? Take the free HProxy proxy list, thousands of live residential, datacenter and mobile IPs, refreshed around the clock.
Scale
When the list getsreally long
A hundred thousand proxies is a lot of connections, and the answer is not to make you wait for all of them. Verdicts stream back one at a time, so the table fills while the run is still going and you can start copying working proxies before it finishes.
If you would rather not send your list anywhere at all, the HProxy Checker desktop app runs the same engine locally, on your own connection, with your own thread count. It is free and open source, and it is the right tool for testing proxies on a private network, which this page refuses to do on purpose.
Building something instead? The HProxy API exposes the same checker, and the paid pools start at $0.65 per GB with city-level targeting and sticky sessions.
After the check
Keep the ones that worked.Stop re-testing the rest.
A free list is a snapshot, and this page has just shown you how much of one survives contact with a real connection. If the same names keep dying on you every morning, the fix is not a better checker.
The upgrade
Residential proxies
$0.65per GB, and the balance never expires
Clean pools with city-level targeting and sticky sessions, running on the same network that just probed your list. You stop re-checking a file every morning, because the addresses are not shared out from under you.
Elsewhere on HProxy
Free proxy list
Thousands of live residential, datacenter and mobile IPs, verified around the clock. Something to test.
Datacenter and ISP
Dedicated IPs priced per address rather than per gigabyte, for work that needs a stable, fast exit.
Mobile proxies
Carrier IPs for the targets that treat everything else as a bot.
API and docs
The same checker and the same pools, wired straight into your own code.
Pricing
Every product on one page, with the volume ladder spelled out.
Questions
Proxy checker FAQ
The nine things people actually ask, answered without marketing. If yours is not here, the live chat on this page reaches the people who run the network.
What is a proxy checker?
A proxy checker tests a list of proxy servers and tells you which ones are actually usable. It connects through each one and reports whether it responds, how fast it is, what protocol it speaks, where it exits, which network owns it, and how much of your identity it leaks. HProxy's checker does all of that free, with no account and no cap on how many lists you test.
How many proxies can I check at once?
Up to 100,000 in a single run. Results stream back as each proxy answers rather than waiting for the whole batch, so a large list starts filling the table within seconds instead of leaving you at a spinner. There is a daily volume budget per network to stop the tool being farmed as free infrastructure, and it refills continuously.
Is it really free, and do I need an account?
Yes and no, in that order. No signup, no API key, no card. We run one of the larger live proxy networks on the internet, so checking proxies is something our infrastructure already does every second of every day, and opening it up costs us close to nothing.
Which proxy types does it support?
HTTP, HTTPS, SOCKS4 and SOCKS5, with or without a username and password. The protocol is detected from the handshake rather than assumed from the port, so you can paste a mixed list without labelling anything.
What do Elite, Anonymous and Transparent mean?
They describe how much the proxy gives away. Elite forwards no proxy headers at all, so the site sees a normal visitor. Anonymous hides your IP but admits a proxy is in the path. Transparent forwards your real IP, which defeats the point. For almost every use case you want Elite.
Why do dead proxies still show a country and a network?
Because geolocation is a property of the IP address, not of whether the proxy answered. We enrich every row before testing liveness, so even a dead endpoint tells you which network it belonged to. That is often the most useful thing about a failed list: if every dead proxy sits in the same ASN, the whole range is gone.
Can I check proxies on my own network?
Not through this page. Loopback, private and link-local addresses are refused before any connection is attempted, which stops the public checker being pointed at internal infrastructure it has no business reaching. For local ranges, use the desktop app, which runs the probes from your own machine.
Does checking a proxy use it up or log it?
Checking opens one short connection per protocol and closes it. It does not consume bandwidth from any plan and it does not add your proxies to the public free list. What you paste is yours.
Where can I get proxies to check?
Start with the free HProxy proxy list: thousands of live residential, datacenter and mobile IPs, verified around the clock. If you need pools that stay clean instead of ones you have to re-check every morning, the paid network starts at $0.65 per GB.