Proxy tools

HTTP proxy checker

Test HTTP proxies specifically. Each proxy must accept a CONNECT tunnel and complete a TLS request to be marked as working.

Formats: host:port · host:port:user:pass · user:pass@host:port. Credentials are used only for this test and are not stored.

How it works

What this tool does

  1. CONNECT tunnel

    We send an HTTP CONNECT request to your proxy for a reference HTTPS host.

  2. TLS inside the tunnel

    Once the tunnel opens we perform a TLS handshake through it.

  3. Exit IP and timing

    We read the IP the reference service reports and measure total time.

How to read the result

  1. HTTP proxies that refuse CONNECT may still handle plain HTTP but cannot carry HTTPS, so they fail here by design.

  2. A 407 response means authentication is required or wrong; check the username, password or whitelist.

In depth

The details that decide the outcome

CONNECT in depth: the request, the status line and the blind tunnel

For HTTPS, the client wants the proxy to relay encrypted bytes it cannot read, so it asks for a tunnel instead of a page. This tool sends the request line CONNECT api.ipify.org:443 HTTP/1.1 with a Host header and, when you supplied credentials, a Proxy-Authorization: Basic header carrying base64 of user:pass. The proxy answers with a status line. A 200 means the tunnel is open and every later byte is relayed unread; 407 asks for authentication; anything else is a refusal, reported as connect_denied.

After the 200, the tool starts TLS through the tunnel with the reference host as the server name and sends one request. Two consequences follow. A proxy that only forwards plain HTTP with absolute-URI requests, and refuses CONNECT, fails here by design because it cannot carry HTTPS. And many proxy servers restrict CONNECT to port 443 by default, which is exactly the port tested, so a pass confirms the one thing HTTPS browsing needs, not every port your application may use. Test other target ports with your real client.

Worked reading: 407, other refusals and credential parsing

A 407 means the proxy wants credentials it did not get or did not accept, and the tool shows an authentication failure. Before retrying, check how the line was parsed. The parser splits user:pass@host:port at the last @ and the first colon, and it does not decode percent-escapes, so enter the password exactly as issued. A password containing a colon works in the user:pass@host:port form but breaks the four-part host:port:user:pass form, which expects exactly four fields. If the credentials are right and you still see 407, the proxy may expect a whitelisted source address instead.

Any other non-200 status means the proxy understood the request and refused it. A 403 is common: the account may be expired or suspended, the destination may be blocked by the proxy’s rules, or access may be limited to whitelisted addresses. Compare by running curl with the -x option and the same credentials from your own network. If the tunnel opens but the result is a TLS failure, something in the path closed or altered the connection, such as a filtering device. If TLS works but no IP is returned, the echo service reply was empty or blocked.

Proxy replyTool resultWhat to do
407 Proxy Authentication RequiredauthRecheck user, password and whitelist; see the parsing notes above.
403 or another non-200 statusconnect_deniedCheck account status, destination rules and source-address limits.
Not an HTTP status linenot_http_proxyThe port may be SOCKS5; try the SOCKS5 checker.
No reply before the deadlinetimeoutCheck host, port and firewalls with the port checker.
200, then a TLS errortlsA device in the path is interfering; retry, then ask the provider.

FAQ

Tool questions

What is the difference from the general checker?

This one only tries HTTP; the general checker can auto-detect HTTP and SOCKS5.

Does HTTPS work through every HTTP proxy?

Only through those that allow CONNECT to port 443.

Is the credential format important?

Use user:pass@host:port or host:port:user:pass.

Does a pass prove that plain HTTP sites will also load?

Not strictly. A pass proves CONNECT to port 443 and a working TLS request, which is what HTTPS browsing needs. Plain HTTP uses a different request form. Most proxies that allow CONNECT also forward HTTP, but load a real http:// page through the proxy to be sure.

Which credential format is safest to use?

user:pass@host:port. The tool splits credentials at the last @ sign and the first colon, which copes with colons in passwords. In the host:port:user:pass form, an extra colon changes the field count and the line is rejected as badly formatted.

Not sure which plan fits?

Describe your use case and target countries and we will recommend a product — or tell you honestly when another type suits you better.