SOCKS5 · mobile and residential
SOCKS5 proxies. One GB balance.
Buy SOCKS5 proxy traffic by the GB for a client that supports username and password authentication. Choose a mobile 4G/5G or residential connection, then set the country and rotation in your username. Both pools are shared.
Before you buy
Check the protocol and the login method.
SOCKS5 authentication
Your application must support SOCKS5 with a username and password. A SOCKS5 address field alone does not establish that it supports the required login method. Check the exact application and version you will run.
The country you need
Check current country availability in your chosen pool. A country selector is a request to use that route, not a reservation of capacity. Keep a plan for incomplete checks when availability changes.
Your permitted workload
Confirm the destination and workflow are allowed, then test a small request from the real application. A successful echo checks one connection; it does not prove that a whole collection or browser job will work.
Use curl for an initial SOCKS5 check, or follow the Python Requests guide for its SOCKS dependency and configuration. Browser and system proxy settings can have different authentication limits. If your application supports authenticated HTTP proxies instead, the same traffic balance also works over HTTP.
Choose the exit network
Two shared pools, the same SOCKS5 connection format.
Mobile 4G/5G
Choose the mobile pool when a permitted test needs a carrier-network exit. The browser, device, language and account state remain separate settings; the network route does not make a desktop application behave like a phone.
Explore mobile proxy traffic →Residential
Choose the residential pool when your task calls for a peer-network connection. It uses opt-in devices with a mix of home broadband and mobile connections. Check the current pool listing for the country needed by your job.
Explore residential proxy traffic →You buy traffic rather than a list of reserved IP addresses. One credential and balance cover both pools. The username selects the pool, country and rotation; changing from HTTP to SOCKS5 does not buy a different pool. View current locations and availability.
First connection
Copy the full username. Enter the password when prompted.
Open the connection builder, select SOCKS5 and your available pool and country, then copy the complete generated username. In the command below, replace only PASTE_FULL_PROXY_USERNAME with that value. Run it in an interactive terminal; curl asks for the proxy password separately. Keep the password out of the command and shell history.
curl --disable --silent --show-error --noproxy '' \
--connect-timeout 5 --max-time 15 \
--proxy "socks5h://gw.portproof.org:7001" \
--proxy-user "PASTE_FULL_PROXY_USERNAME" \
"https://api.portproof.org/v1/echo-ip"This uses SOCKS5 on port 7001, with a five-second connection limit and a fifteen-second overall limit. The limits bound the check; they are not speed promises. Confirm the returned IP field, then repeat a small permitted check from your application. The full curl guide explains how to interpret failures and compare a route.
In curl, socks5h:// passes the destination hostname to the proxy for resolution; socks5:// resolves it locally. This does not verify the resolver’s location or the exit country. See curl’s DNS option reference. SOCKS5 username/password authentication does not encrypt the connection to the gateway, as RFC 1929 explains. Keep HTTPS and certificate verification enabled for HTTPS destinations.
Rotation
Match the session to the job.
Independent observations
Use per-connection rotation when the task does not need one continuing proxy session. A new application request can reuse an existing connection, so request count and connection count are different. Exit addresses can repeat.
A sequence that needs continuity
Use a named sticky session for a permitted multi-step check. Keep the application’s state with that session. The same device is used while available; its IP may change and it may disconnect. Record an interrupted observation before retrying.
Price per GB
Buy traffic for the workload you have measured.
| Order size | Per GB | Saving | Example total |
|---|---|---|---|
| 1 to 4 GB1 GB = EUR 4.50 | EUR 4.50 | ||
| 5 to 24 GB5 GB = EUR 19.50 | EUR 3.90−13 % | ||
| 25 to 49 GB25 GB = EUR 87.50 | EUR 3.50−22 % | ||
| 50 to 99 GB50 GB = EUR 160.00 | EUR 3.20−29 % | ||
| 100 to 249 GB100 GB = EUR 290.00 | EUR 2.90−36 % | ||
| 250 GB and more250 GB = EUR 625.00 | EUR 2.50−44 % |
Start with a small test
The current paid trial is 0.5 GB for EUR 2.90, once per customer. Test the actual client, destination and result before increasing the workload.
Review the paid trial →Scale a useful result
Measure transferred data and complete observations, including resources and retries. Use the bandwidth calculator for planning, then compare the estimate with account usage. Client byte counts and the billing meter may measure different things.
GB never expire. Both pools use the same GB balance. See all order conditions and payment options before buying.
Scope
Confirm support for the operation you need.
These examples cover a TCP connection carrying an HTTPS request. They make no claim of UDP, QUIC or support for every application and destination port. Changing protocol does not change the acceptable-use policy or a destination’s access rules. Choose a permitted price-monitoring, market-research, verification or QA workflow, and stop when access is refused.