Under the hood
Public proxies. Checked with care.
We find public proxies, test HTTPS connections and keep rechecking the pool.
- 01
Discover
Collect publicly listed addresses.
- 02
Verify
Test a real HTTPS connection.
- 03
Return
Return one matching proxy.
What a verification checks.
- 01
TCP connection
We check that the proxy accepts a connection.
- 02
HTTP CONNECT or SOCKS tunnel
We establish an HTTP CONNECT tunnel (for HTTP proxies) or a SOCKS4/SOCKS5 tunnel.
- 03
TLS certificate validation
We complete a TLS handshake and verify the certificate.
- 04
HTTPS response
We request a real HTTPS page to confirm the proxy works.
Verification flow
- TCP connectionProxy accepts a connection
- HTTP CONNECT or SOCKS tunnelEstablish a tunnel to the target
- TLS certificate validationVerify the certificate
- HTTPS responseRequest a real HTTPS page
- Eligible for the poolAdded to the verified pool
Freshness has an expiry date.
45 minDefault recheck interval
60 minDefault maximum verification age
ImmediatelyHidden after a failed recheck
These are the default service settings, not a guarantee that a proxy stays online.
What public proxies can—
and cannot—do.
Useful for
- Scripts and experiments
- Region-specific testing where available
- Repeat requests with different pool selections
Know the limits
- Availability changes
- A later request may return the same proxy
- Handle timeouts and retry in your client
Frequently asked questions.
Is my HTTPS connection verified?
HTTPS checks use certificate validation. Public proxies may still go offline later.
Does a country filter guarantee availability?
No. The filter picks from proxies that are live right now; when none match, the API answers
{"error":"no more proxies left"}.Is this a private proxy network?
No. Every proxy is a public open proxy run by someone else. We only find and verify them.