---
title: "Proxy Checker: Test HTTP & SOCKS5 Proxies Online"
description: "Check up to 20 HTTP, HTTPS or SOCKS5 proxies at once: status, exit IP, country and response time in seconds. Supports user:pass authentication."
url: https://proxonym.com/proxy-checker
updated: 2026-10-01T21:01:06+00:00
---

# Proxy checker: test your proxies in seconds.

Paste up to 20 proxies and see which ones work, the IP and country websites see, and how fast each one answers.

- HTTP, HTTPS & SOCKS5
- User:pass authentication
- Nothing is stored
- **Status** Working, or the exact reason it failed
- **Exit IP** The address target sites see
- **Country** Where that IP is located
- **Latency** Full request time through the proxy

## A real request through every proxy.

No ping tricks: the checker sends an HTTPS request through each proxy, exactly like your scraper would, and reads what comes back.

1. **Paste your list**: Any common format, with or without credentials. Lines starting with # are ignored.
2. **We connect through each proxy**: Up to 20 proxies are tested in parallel against a neutral endpoint, with the timeout you choose.
3. **Read and copy the results**: Status, exit IP, country and latency per proxy. Copy the working ones in one click.

## Proxy formats the checker reads.

One proxy per line, with or without credentials. Hostnames, IPv4 and IPv6 addresses all work.

| Format | Use it for |
| --- | --- |
| `host:port` | No login, or an IP whitelist |
| `user:pass@host:port` | Username and password |
| `host:port:user:pass` | Lists exported by most providers |
| `socks5://user:pass@host:port` | Forcing SOCKS5 (or `http://`) |

## What a check does not tell you.

- **Whether your target blocks the IP**: The test goes to a neutral endpoint. A site with strict bot rules can still refuse an IP that passes here.
- **Speed under load**: One request per proxy measures latency, not the throughput of hundreds of parallel connections.
- **How long a rotating IP lasts**: Each check is a single request. Run your own job to see how sessions hold over time.

## What the errors mean.

Most failures come down to a handful of causes. Here is how to fix each one.

- **Timed out**: The proxy did not answer in time. It may be overloaded, offline or far away; try a longer timeout.
- **Connection refused**: Nothing listens on that port. Check the port, or whether the proxy only accepts SOCKS5.
- **Authentication failed (407)**: Wrong username or password, or the proxy only accepts whitelisted IPs.
- **SOCKS5 handshake failed**: The port speaks HTTP, not SOCKS5, or SOCKS5 needs credentials. Switch the protocol.
- **Proxy refused the tunnel**: The proxy blocks HTTPS (CONNECT) requests or the destination. Common on open public proxies.
- **Private or reserved address**: Only public IP addresses can be tested from our servers, never local or internal ones.

## Done chasing dead proxies?

Proxonym residential and ISP proxies come with a 99.9% uptime target, 195+ countries and a dashboard that handles refunds and IP replacements.

### What does the proxy checker test?

For every proxy, the checker opens a real connection through it to a neutral test endpoint and reports whether it works, the protocol used, the public IP websites see, the country of that IP and the total response time.

### Which formats can I paste?

One proxy per line, as host:port, user:pass@host:port, host:port:user:pass, or with a scheme such as socks5://host:port. Hostnames and IPv4 or IPv6 addresses are accepted.

### Do you store the proxies or credentials I test?

No. Proxies and credentials are used for the test request only and are never written to a database or a log. Passwords are masked in the results.

### Why does a working proxy show as failed?

Common causes are an IP whitelist that does not include our checker, wrong credentials (407), a proxy that only accepts SOCKS5 while HTTP was used, or a timeout that is too short for a slow proxy. Try the protocol selector and a longer timeout.

### Is there a limit?

You can check up to 20 proxies per run and about a dozen runs every 10 minutes. The limit keeps the tool fast for everyone. For continuous monitoring, use your own scripts with our documentation as a starting point.

### Can I check SOCKS5 proxies?

Yes. Pick SOCKS5 in the protocol selector or write the scheme, for example socks5://user:pass@host:port. In automatic mode, ports 1080, 1081 and 9050 are tested as SOCKS5 and every other port as HTTP.

### How do I check a proxy without a tool?

Send one request through it from a terminal: curl -x http://host:port -U user:pass https://api.ipify.org prints the exit IP when the proxy works, and an error code when it does not.

### What is a good response time for a proxy?

It depends on the type. Datacenter proxies usually answer in well under a second. Residential and mobile proxies take longer because traffic goes through a home or phone connection, so compare proxies of the same type, from the same country.

### How do I check Proxonym proxies?

Paste gw.proxonym.com:8000 with your username and password, for example USERNAME-country-us:PASSWORD@gw.proxonym.com:8000. The result shows the exit IP and its country, so you can confirm your targeting.
