SOCKS5 Proxies on Mobile Carrier IPs
SOCKS5 is a proxy protocol that relays whole connections without reading them: your tool tells the proxy where to connect, and the proxy passes the bytes through. Every ProxyStream server takes SOCKS5 and HTTP connections, with a username and password or from a whitelisted IP.
From $0.60 for 4 hours
Connection formats in your dashboard
- SOCKS5
- socks5://USERNAME:PASSWORD@HOST:PORT
- HTTP
- http://USERNAME:PASSWORD@HOST:PORT
- Whitelisted IP, once you save one
- HOST:PORT
On a Standard server one port takes both formats. An Advanced proxy gets its own HTTP port and SOCKS5 port.
What Happens When Your Tool Connects
Four short exchanges, then the proxy steps aside. This is RFC 1928, the SOCKS5 standard.
- Your tool to SOCKS5 port: Hello. I can connect without a login, or with a username and password.RFC 1928, section 3
- SOCKS5 port to Your tool: Use username and password.If your IP is whitelisted, no login is asked for.
- Your tool to SOCKS5 port: Here are my username and password.RFC 1929. Sent in plain text.
- SOCKS5 port to Your tool: Accepted.
- Your tool to SOCKS5 port: CONNECT example.com, port 443.Sending the name, not an IP, lets DNS resolve on the proxy side.
- SOCKS5 port to Website: Opens a TCP connection from the carrier IP.
- SOCKS5 port to Your tool: Connected.
- Your tool to Website: Your traffic, relayed as is. With HTTPS, the proxy sees only encrypted bytes.
SOCKS5 or the HTTP Port
Both reach the site from the same carrier IP. They differ in what they carry.
What it carries
- HTTP proxy
- HTTP requests, and HTTPS through a CONNECT tunnel
- SOCKS5
- Any TCP connection; UDP too on Advanced servers
How your tool names the site
- HTTP proxy
- In the request, or as host:port for CONNECT
- SOCKS5
- As a hostname or an IP in the CONNECT request
Where DNS is looked up
- HTTP proxy
- By the proxy, from the hostname you send
- SOCKS5
- By the proxy when you send a hostname (socks5h:// in curl); by you when you send an IP
Use it when
- HTTP proxy
- A tool only takes HTTP proxies, or a browser can't send a SOCKS5 password
- SOCKS5
- Non-web protocols, apps that speak SOCKS, or UDP and HTTP/3
On a Standard server one port answers both protocols. An Advanced proxy gets a separate HTTP port and SOCKS5 port.
Connecting From Code
Replace the capitals with the host, port and login from your dashboard.
# curl: socks5h:// resolves the hostname on the proxy side
curl --proxy "socks5h://USERNAME:PASSWORD@HOST:PORT" https://ipinfo.io/json
# Python (pip install "requests[socks]")
import requests
proxies = {"https": "socks5h://USERNAME:PASSWORD@HOST:PORT"}
print(requests.get("https://ipinfo.io/json", proxies=proxies).json())
# A whitelisted IP needs no login
curl --proxy "socks5h://HOST:PORT" https://ipinfo.io/jsonSome browsers and automation tools accept a SOCKS5 proxy but can't send its username and password. For those, whitelist the IP you connect from in the dashboard, or use the HTTP form of the same proxy.
Your Password Travels in Plain Text
That is how SOCKS5 logins are defined. Here is what it does and doesn't expose.
RFC 1929, the SOCKS5 username and password method, sends both in the clear. Someone able to watch the network between you and the proxy could read them. What travels after the login is up to you: an HTTPS connection through the proxy stays encrypted end to end, and the proxy only relays it.
Whitelisting your IP avoids sending a password at all. It suits a fixed office or server address; on a connection whose IP changes, you would have to update the whitelist each time.
UDP, QUIC and HTTP/3
Carried on Advanced servers only: 3 servers on sale now.
HTTP/3 runs on QUIC, and QUIC runs on UDP, not TCP. An HTTP proxy and a plain SOCKS5 CONNECT both carry TCP only, so a browser behind them falls back to HTTP/2 or HTTP/1.1. SOCKS5 has a second command, UDP ASSOCIATE, that relays UDP datagrams instead.
Advanced servers support it, so UDP traffic, QUIC and HTTP/3 included, leaves from the mobile IP like everything else. Use one when your tool needs UDP, or when you want a site to see HTTP/3 traffic the way it would from a phone.
Servers on Sale
Every one takes SOCKS5. The Advanced rows also carry UDP.
Verizon · California
5G Standard · Every 45 min
Sold for 4 hours to 1 month
From $0.60Verizon · Florida
5G Standard · Every 30 min
Sold for 4 hours to 1 month
From $0.60Verizon · New York
5G Standard · Every 30 min
Sold for 4 hours to 1 month
From $0.60Verizon · New York
5G Advanced · When you open your rotation link
Sold for 1 day to 1 month
From $3.00Verizon · Virginia
5G Standard · Every 10 min
Sold for 4 hours to 1 month
From $0.60Verizon · Washington
5G Standard · Every 60 min
Sold for 1 day to 1 month
From $1.00T-Mobile · California
4G Standard · Every 30 min
Sold for 4 hours to 1 month
From $0.60T-Mobile · New York
4G Standard · Every 30 min
Sold for 4 hours to 1 month
From $0.60T-Mobile · Pennsylvania
5G Standard · Every 30 min
Sold for 4 hours to 1 month
From $0.60T-Mobile · Texas
5G Standard · Every 30 min
Sold for 4 hours to 1 month
From $0.60T-Mobile · Texas
4G Standard · Every 45 min
Sold for 4 hours to 1 month
From $0.60AT&T · Michigan
5G Advanced · When you open your rotation link
Sold for 1 day to 1 month
From $3.00AT&T · New York
4G Standard · Every 50 min
Sold for 4 hours to 1 month
From $0.60AT&T · Texas
5G Standard · Every 30 min
Sold for 4 hours to 1 month
From $0.60Three · London
5G Standard · Every 25 min
Sold for 4 hours to 1 month
From $0.60Three · Manchester
5G Advanced · When you open your rotation link
Sold for 1 day to 1 month
From $3.00O2 · Hanover
5G Standard · Every 15 min
Sold for 1 week to 1 month
From $5.00
Related Guides
Sources
Copy last checked 26 October 2026. Server lists and prices on this page load from the live catalog.
Point Your Tool at a Carrier IP
Rent a proxy for 4 hours, paste the SOCKS5 string from your dashboard, and check the address with one curl call. From $0.60 for 4 hours.
Choose a Server