cURL Proxy Setup

Flags that matter

curl is the fastest way to prove an address works before you write any code. Both of our address types plug in the same way:

Put credentials in the -x argument or keep them out of shell history with --proxy-user and a netrc file.

Checking what the target sees

Three commands worth keeping around: confirm the exit address, confirm geography, confirm the session holds:

Shell: verify address, geography and stickiness

# which address are we leaving from
curl -x login_c_US:password@proxy.sotaproxy.com:10000 https://api.ipify.org

# what the target sees about that address
curl -x login_c_DE:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json

# does the sticky session hold across calls
for i in 1 2 3; do
  curl -s -x login_c_US_s_9_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
  echo
done

# SOCKS5 with DNS resolved on our side
curl -x socks5h://login:password@proxy.sotaproxy.com:10000 https://api.ipify.org

• Three identical answers from the sticky loop mean the session works. Three different ones mean a suffix is malformed and you silently got rotation.
• Add -v when something is wrong. The proxy handshake is visible there and a 407 is unmistakable.
• Use --compressed to ask for gzip and save residential traffic while testing.
• For static addresses drop the suffixes entirely and point curl at your-ip:50100, or 50101 for SOCKS5.

curl specifics