From source to published result
- Collect: fetch the published ProxyScrape and monosans datasets over HTTPS. Keep source names attached to each endpoint.
- Validate: accept public IPv4 addresses, valid ports and supported HTTP, SOCKS4 or SOCKS5 protocols. Reject private addresses, credentials and malformed records.
- Deduplicate: use protocol, IP and port as the endpoint identity. Seeing the same endpoint in two feeds does not count as two proxies.
- Check: establish a direct IP baseline, then request the ipify HTTPS IP endpoint through the proxy. Make a second HTTPS request to Cloudflare’s trace endpoint. Both requests must succeed with normal certificate validation, and both reported exit addresses must differ from the checker’s direct addresses.
- Publish: send the signed result to the catalog. The website itself does not connect to proxy endpoints.
Two local checkers, bounded requests
Two independent local computers share the candidate queue using a deterministic assignment. Each endpoint is normally checked by one assigned computer; two online checkers do not mean that every row has passed on both. The checker label in each row identifies the measuring node.
Each node runs at most six concurrent checks. Probes have short connection and overall timeouts and a small response-size limit. They use application-level proxy settings without changing system routes, VPN connections or the desktop browser. No account cookies or personal traffic are included in a probe.
Freshness, latency and observed success
Successful endpoints become eligible for another check after 15 minutes, subject to queue load. Source lists are fetched approximately every 30 minutes. A failed recheck removes an endpoint from that node’s next published snapshot. Results expire after one hour even if a node stops reporting.
Latency is the elapsed time for the first HTTPS request, including connection setup and response transfer. It is not ICMP ping or download speed. Observed success is successful attempts divided by all attempts recorded by the assigned checker. One success out of one attempt is limited evidence; it is not a long-term uptime promise.
What passing does not establish
We do not verify ownership, consent of the endpoint operator, logging practices, residential status, unrestricted access, streaming support or sustained bandwidth. Location is source-reported endpoint geolocation, which can differ from the exit address. We do not label a proxy anonymous or elite based on a source claim. UDP support and DNS leak behavior are not tested by these TCP probes.
Measurements can differ by network, destination and time. Use the troubleshooting guide if a listed proxy fails from your connection. Report removal requests through Contacts.