PhantomIntegration
How to Test a Proxy Safely
Test a proxy in layers: confirm the gateway connection, inspect the observed exit IP, check the requested country, and then repeat a small request to evaluate rotation or stickiness. This separates credential problems from destination-specific blocking.
Start with a single cURL request
Use a simple IP-information endpoint rather than the final destination. Replace the placeholder URL with the complete HTTP(S) or SOCKS5 proxy URL generated in your dashboard.
curl --fail --show-error --max-time 30 \
--proxy "$PROXY_URL" \
https://ipinfo.io/jsonValidate the result
A successful HTTP response only proves that some path worked. Inspect the returned IP and country, then compare repeated requests according to the selected rotation mode.
- The observed IP should differ from your direct public IP.
- The country should match your selected target when that route is available.
- A sticky session should usually repeat the same IP.
- Rotating mode should be evaluated over several requests, not one.
Measure useful latency
Time a small number of representative requests and record median and slow-tail behavior. Residential routes vary, so one unusually fast or slow request is not a reliable benchmark.
curl --silent --output NUL \
--write-out "connect=%{time_connect}s total=%{time_total}s\n" \
--proxy "$PROXY_URL" \
https://example.com/Interpret common failures
An authentication error points to the username, password, or malformed configuration tags. A connection refusal often indicates the wrong protocol port. A timeout can mean a temporary route shortage, network issue, or slow destination.
If an IP check succeeds but one website fails, the destination may be restricting the route. PhantomProxies does not guarantee access to a particular website. Test another neutral endpoint before rotating credentials or contacting support.