How the proxy list works

Each entry shows a proxy’s connection details and latest recorded check. Check times and labels help you choose an endpoint; availability can change.

On this page

A 15-minute freshness limit

Every published endpoint must have a valid check timestamp less than 15 minutes old. We validate the address and port, remove duplicate endpoints, and exclude expired records before rendering a page or export.

Use Checked within to narrow the list to checks less than 1, 5 or 10 minutes old. This shorter limit also applies to copies, selections, API results and exports. It remains enforced when automatic refresh is paused. The filter describes the age of recorded evidence; it does not run a new connection test.

Check timestamps use UTC. The table shows their age, with the exact UTC timestamp available on hover. They describe the recorded network check, not the time a page was opened. With JavaScript enabled, a visible list refreshes once a minute without reloading the page. You can pause automatic refresh; expired entries are still removed from the table and from selections.

A refresh keeps the current filters and the selected endpoint’s request settings. Selections remain only for endpoints still on that page. If a refresh fails, current entries stay available until their checks expire and the list shows when a retry is possible. A downloaded file is a snapshot and cannot update itself.

Recorded checks and their limits

A check records whether a proxy responded at a particular time. Your result may differ because the network path, destination and timing differ.

Open an address and expand Check evidence. When a 24-hour history is available, it shows the number of passed and failed checks, the total observations and the window. The percentage is passed checks divided by total checks; it does not measure continuous uptime or describe how evenly checks were spaced.

When that history is unavailable, the panel says Latest check only. A recent timestamp or a low response time cannot establish an uptime percentage. Unavailable measurements stay unknown.

HTTP, HTTPS, SOCKS4 and SOCKS5

Protocol labels reflect recorded support for HTTP, SOCKS4 or SOCKS5. An endpoint may support more than one protocol. The HTTPS label requires an HTTP endpoint with an explicit successful CONNECT result and certificate validation; a generic SSL flag alone is insufficient.

HTTPS here means an HTTP proxy can tunnel to an HTTPS destination. It does not mean the proxy URL starts with https://. Read the protocol guide before configuring a client.

What the other columns mean

Country
An IP geolocation estimate. It is not proof of the operator’s identity or physical location.
Response time
A recorded response duration in milliseconds. It is not download throughput and does not predict every destination’s response.
Anonymity
A classification based on what a connection check could observe. Elite indicates no detected proxy or origin-IP disclosure in that classification; anonymous indicates proxy use was detectable without an observed origin-IP disclosure; transparent indicates an origin-IP disclosure. Unknown means no supported classification was supplied. These labels cannot guarantee anonymity.

What happens when data is unavailable

When recent check results are unavailable, the list asks you to try again later. Expired entries are excluded from pages, downloads and API responses.

If your filters have no matches, the directory keeps your choices visible. Suggested alternatives show how many endpoints match after removing just one filter, while retaining the protocol and other choices. You can also remove an individual filter or clear them all.

The country comparison counts each endpoint once in its total. Protocol counts overlap when an endpoint supports more than one protocol; HTTPS CONNECT endpoints also appear under HTTP. These are inventory counts at page load, not quality or uptime scores.

Use the results with context

Public proxies are operated by third parties. A successful check does not establish permission to use an endpoint, its operator’s intentions, or access rights at a destination. Keep sensitive traffic away from unknown operators and use only networks and services you are authorized to access.

See data use and troubleshooting.