Queue-based check
Free Proxy Checker Online
One endpoint per line: IP:PORT or IP:PORT:LOGIN:PASSWORD. Maximum 50. Checks HTTP, HTTPS, SOCKS4 and SOCKS5.
Queue-based check
One endpoint per line: IP:PORT or IP:PORT:LOGIN:PASSWORD. Maximum 50. Checks HTTP, HTTPS, SOCKS4 and SOCKS5.
Proxy checker is an online program that provides proxy verification regarding server validity and anonymity.
Our tool verifies proxies in 3 simple steps:
1. Input Data: Enter up to 50 IP:Port addresses (e.g., 72.49.49.11:8080) in the text field, one per line.
2. Automated Validation: The system tests each proxy across 7 key parameters:
- Validity (Valid/Not Valid).
- Geo-Location (Country & City).
- Connection Speed (in milliseconds).
- Proxy Type (HTTP, SOCKS4, SOCKS5).
- Anonymity Level (Transparent, Low, Distorting, High).
- Special Offers — for invalid proxies, we recommend purchasing reliable proxies.
3. Results: A detailed table with instant download options: CSV and TXT formats.
Every row the checker returns answers four separate questions, and they fail independently. Status says whether a TCP connection was opened and a request came back at all. Protocol says what the endpoint actually spoke — a proxy sold to you as SOCKS5 that only answers HTTP CONNECT is not a broken proxy, it is a mislabelled one. Country is resolved from the exit address, not from the seller's promise. Delay is the round trip through the proxy to our endpoint, so it includes the proxy's own processing time, not just the network hop.
The column worth the most is anonymity, and it has three values rather than two. Transparent means the proxy forwarded an address that sits in front of it — usually yours. Anonymous means it announced itself with a proxy header but did not pass an address along. None detected does not mean "no proxy": it means that from the server's side an elite proxy and a direct connection look identical, which is exactly what an elite proxy is for.
The list you paste becomes a job in a queue, and a worker walks it. For each endpoint the worker opens a connection, negotiates the protocol, and then requests a signed endpoint on our own domain through the proxy. That endpoint reports back every address and proxy header it received — which is how anonymity is judged on evidence rather than on what the proxy claims in a banner.
Geolocation comes from a local database on our server, not from a third-party API, so no part of your list is sent anywhere to be looked up. Passwords are never written to the export file. Up to 50 proxies go through in one batch.
You bought a list and want to know what share of it is alive before you build anything on it.
A scraper started returning blocks and you need to tell a dead proxy apart from a blocked one.
A provider promised residential IPs in one country and you want to see what the exit addresses actually resolve to.
You are about to rotate a pool and want the slow endpoints out of it first.
A proxy that answers us is not a proxy that will work for your target. Sites keep their own reputation data, and an address that passes here can still be blocked by Cloudflare, by a sneaker site or by an ad platform. The checker also measures a single moment: free and shared endpoints change state within minutes, so a list checked yesterday is not a list you know anything about today. And a proxy hides your address — it does not hide your browser, which is a separate problem you can see for yourself on the browser fingerprint test.
Up to 50 per run. The limit is there because each endpoint gets a real connection and a real round trip rather than a ping, and a batch that takes ten minutes is a batch nobody waits for. Split a larger list and run it in parts.
The list is held for as long as the job runs so the worker can process it, and credentials are stripped from the downloadable result. Geolocation is resolved from a database on our own server, so your addresses are not sent to any third-party lookup service.
That the server saw nothing to suggest a proxy: no forwarded address, no proxy header. For an elite proxy this is the correct and best outcome. It is not a statement that your traffic went direct — the tool reports what a receiving server can observe, and an elite proxy is defined by being unobservable.
Most often it is IP authorisation: the endpoint only accepts connections from an address you whitelisted, and our worker is not on that list. Other common causes are an endpoint that only allows certain destination ports, or one that has simply died since you last used it.
Because we read the exit address and look it up, rather than repeating the label on the listing. Mislabelled geolocation is one of the most common defects in cheap proxy lists, and it is the kind that quietly ruins geo-targeted work while everything appears to function.
No. The check proves the endpoint is reachable, speaks the protocol it claims and hides what it claims to hide. Whether a specific target accepts it depends on that target’s own reputation data for the address, which no external checker can see.