Why test a proxy?
Before starting your task, confirm that the proxy responds, an IP-checking website sees the expected exit address, and your application does not bypass the proxy.
Three levels of checks
1) Connection: does the server respond? 2) Exit address: which IP and country does the website see? 3) Application: are any requests sent directly?
Step 1. Check the connection
The basic check is whether the proxy responds and can reach the internet. You can test this in seconds.
- Configure the proxy in a browser, or use curl or a connection checker.
- Open an IP-checking website, such as 2ip.ru, whoer.net or ipinfo.io.
- If the page loads and shows the proxy IP, the connection is working.
- If it fails to load or times out, check the host, port, username and password.
From the command line
Run curl -x http://login:password@host:port https://api.ipify.org. A returned proxy IP confirms this connection. A connection error means the check failed.
Step 2. Verify the IP and location
Confirm that the proxy has the IP type and location you expect. This matters especially for tasks that depend on location.
- Open whoer.net or ipinfo.io to inspect the IP, country, city, network (ASN) and address classification.
- Compare the country with your selected target. An unexpected country may mean the targeting settings need correction.
- The address type, such as residential, datacenter or mobile, should match your product.
Step 3. Check privacy and leaks
A proxy routes only traffic that your application sends through it. Test browser features and DNS settings separately in the same environment you will use for your task.
- Compare the IP before and after enabling the proxy within the same browser or process.
- If your application uses WebRTC, run a separate check. System proxy settings do not control every browser connection.
- Check DNS in your environment. Resolution behavior depends on the application and selected protocol.
- Do not treat a third-party checker's percentage or label as a guarantee. Location and classification databases can disagree.
If your original IP is visible
Stop the task and check your application, DNS and WebRTC settings. One successful proxy request does not prove that every request goes through it.
Step 4. Test speed and stability
Even a working connection may have unsuitable latency or stability. Measure these on your actual route and target service.
- Measure the full request duration with the same protocol your tool will use.
- Repeat the request and record failures, timeouts and variation in response time.
- Compare products under the same conditions: URL, response size, region and number of parallel requests.
Which checking tools to use
- The Proxly tool checks the connection, exit IP, available location data and response time.
- An IP-checking website confirms the result from your actual browser.
- curl provides a repeatable command-line connection test.
- Separate WebRTC or DNS tests are needed when your environment uses those channels.
Results depend on the route, application and target service. Start with test traffic before running your workload.
Choose a proxy for your task.
Frequently asked questions.
Configure it in a browser and open an IP-checking website, such as 2ip.ru or whoer.net. Confirm that it shows the proxy IP. In a terminal, run curl -x http://login:password@host:port https://api.ipify.org.
These are third-party checker labels describing whether they detect signs of proxy use. Methods and databases vary, so focus on the actual exit IP and tests in your own environment.
WebRTC uses separate browser networking mechanisms and may not follow the system proxy settings. If your task uses it, test it separately in the working profile.
Check the location parameters in your access string. Residential supports countries, cities and provider networks (ASN) from the current catalog. Without location parameters, location follows the product's rules.