Test a proxy before your team relies on it
We send a single test request via the proxy you paste and time the round trip. The result shows whether it answered, the time taken and the exit IP it used.
Before you hand credentials to a colleague
- Copy the host, port, username and password from your dashboard rather than from an old email or chat message.
- Pick the protocol the receiving tool will use: HTTP, HTTPS or SOCKS5.
- Paste the proxy as
ip:port,ip:port:user:passoruser:pass@ip:port. Hostnames are accepted as well as IP addresses. - Note the exit IP and check it in the IP location lookup, so you know it sits in the market you ordered before the details go out.
When the check fails
The line couldn’t be read. Remove stray spaces and use one of the formats listed above.
Usually a mistyped host or port, or the wrong protocol for that port. Copy the details from the dashboard again and retry.
The proxy refused the login. Check the username and password, or whether the order uses IP-whitelist access instead.
Only proxies on public addresses can be tested, so internal network ranges are blocked.
A successful check shows the proxy accepted the login and passed a request on from our server. How a particular website treats that IP is a separate question; for reputation, look the exit IP up in the blacklist checker. The proxy details you paste are used for this one check and are not stored.
