Check the endpoint before running the example
Wait for a ready order, confirm time and traffic remain, and copy the proxy IP, port, username and password. Use an HTTP proxy URL even when the destination starts with HTTPS. The HTTPS connection uses a CONNECT tunnel.
Dropstride supports public destination ports 80 and 443. The HTTP connection to the proxy does not encrypt proxy authentication, so use a trusted network and keep credentials private. Do not share command output containing credentials.
Run a small HTTPS check
The following example uses a POSIX shell on macOS or Linux. Replace the host, port and username placeholders with the active order fields. Run it interactively so curl can prompt for the password. In Windows PowerShell, invoke curl.exe and enter its options on one line.
The example limits connection setup to 10 seconds and the whole request to 30 seconds. A 200 destination status confirms this request completed; it does not prove access to a different website.
#!/bin/sh
# POSIX shell. curl prompts for the password so it is absent from shell history.
# Replace these two placeholders with values from your active order.
proxy='http://IP:PORT'
username='USERNAME'
curl --proxy "$proxy" --proxy-user "$username" \
--connect-timeout 10 --max-time 30 --fail-with-body \
--write-out '\nDestination HTTP status: %{http_code}\n' \
https://example.com
Read the result at the correct layer
A 407 during CONNECT means the proxy rejected or needs authentication. A 403 during CONNECT means the proxy refused that tunnel. A destination HTTP 403 after a successful tunnel is a separate response from the destination.
Our local fixture returned curl exit 56 for a denied CONNECT, exit 28 for a deliberately stalled connection, and destination status 403 for an established tunnel to a denying origin. The exact error text can vary by curl version. --fail-with-body makes the downloadable example fail on HTTP error responses too.
| Result | Next check |
|---|---|
| 407 during CONNECT | Re-copy the endpoint-specific username and password. |
| Timeout / exit 28 | Check readiness, expiry, allowance and network reachability. |
| Destination HTTP 403 | Check the destination response and its access rules. |
| TLS certificate error | Check the destination hostname, device time and CA trust; do not add -k. |
Check proxy bypass and output handling
NO_PROXY or no_proxy can cause selected hosts to bypass the configured proxy. Inspect your environment before assuming every request used the proxy; for a deliberate proxy-only test, curl --noproxy "" removes that bypass list.
Avoid verbose traces in shared logs. Do not put a password in a shell command or reuse an account password as proxy authentication. An exit-IP endpoint, if you choose one, sees the source IP and requested URL.
What we actually tested
On 7 November 2026, a controlled local proxy accepted the authenticated request and relayed it to an isolated HTTP or HTTPS origin. The HTTPS certificate was verified against a local test certificate authority; verification was not disabled. The origin received no Proxy-Authorization header.
This proves the demonstrated protocol configuration in the listed versions. It does not measure a live Dropstride public exit IP, cloud availability, retailer acceptance, purchasing bots, speed or checkout success. After delivery, use a public IP-check service you trust to verify the assigned exit IP separately.
Sources and verification
Tested versions: curl curl 8.7.1 (x86_64-apple-darwin25.0) libcurl/8.7.1 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.12 nghttp2/1.68.1.
Product facts describe the current offer. Protocol sources and controlled tests have the scope stated in the article.
curl proxy options and timeouts ↗ (checked 7 November 2026)curl exit codes ↗ (checked 7 November 2026)Dropstride protocol and product limits ↗ (checked 7 November 2026)