The Proxy Tester lets you check your proxies before you use them, right in your Webshare dashboard. Paste in a list of proxies and in a few seconds you'll see which ones work, which protocol they use, the IP and country they connect from, and how fast they respond. No scripts, cURL or third-party tools needed.
Before you start: you'll need a Webshare account. You can test your Webshare proxies and proxies from other providers.
What does the Proxy Tester check?
For each proxy, the results table shows:
Proxy: the proxy you tested
Target URL: the website or endpoint the proxy connected to
Type: the protocol used, HTTP or SOCKS5
Status: Success, Timed out or Failed. If a test doesn't succeed, a message explains why (see What do the error messages mean? below)
Exit IP: the public IP address the website sees when you use this proxy
Location: the country of the exit IP
Response Time: how long the request took, in milliseconds
How do I test my proxies?
In your dashboard, open Proxy Tester from the left menu.
Optional: enter a Target URL, such as
https://google.com, to check whether your proxies can reach a specific website. Leave it empty to use the default Webshare endpoint.Optional: choose a Protocol. Auto is selected by default and detects the protocol for you. Pick HTTP or SOCKS5 if you want to test one protocol specifically.
Click Add Proxies and paste your proxies, one per line.
Click Submit & Test. Results appear in the table as each test finishes.
To start over, click Clear All.
Supported formats (one proxy per line):
host:port:username:passwordusername:password@host:porthost:port, only for public proxies that don't need a username and password
Good to know: The tests run from Webshare's servers, not from your computer, so IP authorization doesn't work in the Proxy Tester. Always add your proxies with their username and password. You can copy them from your Proxy List, even if you normally connect using IP authorization.
Default endpoint or custom Target URL?
Default endpoint (Target URL left empty): the quickest way to check that a proxy works and see its exit IP, location and speed. Use it for a general health check, for example right after buying or replacing proxies.
Custom Target URL: checks whether your proxies can reach the website you actually plan to use. Use it when a proxy works in general but you're having trouble with one specific site.
How many proxies can I test?
Up to 100 proxies per hour with the default endpoint
Up to 25 proxies per hour with a custom Target URL
The Proxy Tester shows how many tests you have left this hour. If you submit more proxies than you have left, the whole batch is rejected: nothing is tested and none of your allowance is used. You'll see how many tests you have left, so you can reduce the number of proxies and try again. Once you've used the full allowance, you'll see how many minutes are left until you can test again.
Comparing proxies
Because every proxy is tested from the same place against the same target, the Proxy Tester is a fair way to compare proxies side by side. Add proxies from another provider next to your Webshare proxies, use the same Target URL, and compare their status and response time.
What do the error messages mean?
Timed out
The proxy didn't respond before the request timed out: the Proxy Tester couldn't connect to the proxy within 10 seconds. Check the host and port, and try again.
The target didn't respond before the request timed out: the proxy connected, but no response came back within 10 seconds. The target website may be slow, or the proxy accepted the connection and then stopped responding. Try the default endpoint to see whether the proxy itself works.
Failed: a problem with the proxy
The proxy rejected the username or password: the credentials are missing or wrong. Add the proxy in the
host:port:username:passwordformat and check the credentials in your Proxy List. Proxies added without credentials because they use IP authorization also show this message.The proxy could not be reached: the Proxy Tester couldn't connect to the proxy at all. Check the host, port and protocol. For SOCKS5 proxies, a wrong username or password also shows this message.
The proxy host name could not be resolved: the proxy address doesn't exist. Check it for typos.
The proxy does not speak the selected protocol: set Protocol to Auto or pick the other protocol, and test again.
The proxy returned an unexpected error: the proxy responded with an error. Try again in a few minutes. If it keeps happening with a Webshare proxy, see Proxies Are Not Working: Troubleshooting Common Issues.
This host cannot be tested: the proxy address is private or internal, so it can't be tested for security reasons.
Failed: a problem with the target website
The target refused the request coming from this proxy: the website blocked or rate-limited the request. Some proxy providers also block certain websites. See What can I do if the proxies are blocked? and Are there any blocked websites from your end?
The target host name could not be resolved: the Target URL doesn't exist. Check it for typos.
The secure connection to the target could not be established: the HTTPS connection to the website failed. Check the Target URL, or try the same proxy with the default endpoint.
Failed: other
This proxy could not be tested. Please try again: something went wrong on our side while testing this proxy. Test it again.
Other common questions
The Exit IP is different from the proxy address: this is expected with rotating proxies, where the exit IP can change with each test.
The location isn't what you expected: see What can I do if the proxy country doesn't match the one on Webshare?
Response times are high: response time includes how quickly the target website answers, so it varies by site. See Troubleshooting Slow Proxy Speed.
Your proxies pass the test but don't work in your app: the issue is likely in your app's proxy settings or network. If you connect with IP authorization, check that your current IP is authorized. See Proxies Are Not Working: Troubleshooting Common Issues.
Need Assistance?
If you have any questions, our Customer Support team is here to help. Reach out at [email protected].