Proxy Tester

The proxy refused the login (407)

The username or password is wrong. Copy them again from your provider’s dashboard, including any targeting part of the username such as a country or session.

The proxy asked for a login (407)

The proxy needs a username and password and the line had none. Use host:port:username:password or username:password@host:port.

Could not connect to the proxy

Nothing accepted the connection on that host and port within 8 seconds. Check the host, the port and the protocol, and whether the proxy only allows IPs you added to an allow list.

The proxy closed the connection

The proxy hung up without an answer. This usually means the wrong protocol, for example a SOCKS5 port tested as HTTP, or a login it did not accept.

The request timed out after 15 seconds

The proxy accepted the connection but the request did not finish in time. The proxy or its upstream is overloaded, or the route is very long.

The proxy refused the request (HTTP …)

The proxy answered with an error code of its own, for example 403 when its rules block the destination.

Not with a page from the internet (HTTP …)

Something answered, but it did not return the exit IP. The address is probably a web server, not a proxy, or the protocol is wrong.

The tester is busy

A few tests run at the same time on our server. Wait a few seconds and run it again.

Checking a rotating or sticky setup. Run the test two or three times with the same line. A rotating proxy should show a different exit IP on each run. A sticky session, usually set with a session ID in the username, should keep the same exit IP until it expires. For country or city targeting, add the targeting to the username the way your provider documents it and check that Location matches.

Proxy hostnames have to resolve to an IPv4 address, and private or local addresses are refused because the test runs from our server on the public internet. To check many open proxies at once instead, use the Proxy Checker.