Using your proxy

Connect via SOCKS5

Each proxy port speaks one protocol — SOCKS5 or HTTP(S) — chosen when you create it. SOCKS5 (via socks5h://) is the right default for most tools; create an HTTP(S) port (http://user:pass@host:PORT) for tools that only speak HTTP — one of each if you need both. Ports on the same device share its carrier exit IP and rotate together. Anything that speaks either protocol can use them — browsers, scrapers, antidetect browsers, curl.

Use socks5h, not socks5

The h makes DNS resolve through the proxy — on the phone's carrier network. Plain socks5:// leaks your DNS lookups from your own machine, which defeats the point and can reveal your real location.

curl

curl -x socks5h://USERNAME:PASSWORD@GATEWAY:PORT \
     https://api.ipify.org?format=json

HTTP(S) instead of SOCKS5

Prefer an HTTP proxy? Create a proxy port with protocol: http — it gets its own port and credentials. It carries HTTPS via CONNECT, so your traffic stays end-to-end encrypted. If a tool needs both protocols, create one port of each — they share the device's exit IP and rotate together.

curl -x http://USERNAME:PASSWORD@GATEWAY:PORT \
     https://api.ipify.org?format=json

Python (requests)

Install the SOCKS extra: pip install "requests[socks]".

import requests

proxy = "socks5h://USERNAME:PASSWORD@GATEWAY:PORT"
r = requests.get(
    "https://httpbin.org/ip",
    proxies={"http": proxy, "https": proxy},
    timeout=30,
)
print(r.json())

Node.js

import { SocksProxyAgent } from "socks-proxy-agent";

const agent = new SocksProxyAgent(
  "socks5h://USERNAME:PASSWORD@GATEWAY:PORT"
);
const res = await fetch("https://api.ipify.org?format=json", { agent });
console.log(await res.json());

Antidetect browsers & other tools

Most multi-account and antidetect browsers (and scraping frameworks) have a proxy field. Choose SOCKS5, then fill in the host, port, username, and password from your proxy — or paste the whole socks5h://user:pass@host:port URL where a single "proxy URL" is accepted.

One phone, many tools

Mint a separate credential for each tool or customer so you can watch and revoke each independently — see Managing credentials. They all share the phone's single carrier IP.

What's blocked

Private and link-local ranges (SSRF protection) and known-abusive destinations are filtered at the gateway before they reach your phone. Legitimate target blocked by mistake? Tell us — our filters are auditable.