Protocols

SK5, HTTP and HTTPS. Your stack, not ours.

Use the protocol your tools already support. The same mobile IPs and the same credentials work across all three.

Choose your protocol

Three ways in. One mobile pool.

You do not need a new toolchain. Point your existing browser, script or API client at the protocol you already use.

SK5 / SOCKS5

Full TCP proxy for browsers, automation and CLI tools. UDP is available on request. Username/password auth.

HTTP

Standard HTTP proxy for legacy clients and simple integrations. Same mobile IPs, same credentials.

HTTPS

HTTPS CONNECT for encrypted traffic. The proxy carries the tunnel; it does not need to read your payload.

Authentication

Credentials built for automation.

Every order gets its own username and password. No shared open proxy, no IP-only trust.

Per-order username and password
Works across SK5, HTTP and HTTPS
Rotate or pin a session from the username
Keep credentials out of client-side code

A note on safety

Treat proxy credentials like any other secret. Store them server-side, rotate them if they leak, and never ship them in a public frontend bundle.

Need IP allowlisting or a different auth model? Ask during onboarding.

Copy, paste, test

The three snippets teams ask for first.

Replace USER, PASSWORD, GATEWAY_HOST and PORT with the credentials from your onboarding email.

curl · SK5

curl -x socks5h://USER:PASSWORD@GATEWAY_HOST:PORT \
  https://ipinfo.io/json

curl · HTTP

curl -x http://USER:PASSWORD@GATEWAY_HOST:PORT \
  https://ipinfo.io/json

Python · requests

import requests

proxies = {
    "http":  "http://USER:PASSWORD@GATEWAY_HOST:PORT",
    "https": "http://USER:PASSWORD@GATEWAY_HOST:PORT",
}
print(requests.get("https://ipinfo.io/json", proxies=proxies, timeout=20).json())

Start with a live mobile IP test.

Send your target countries, monthly volume and protocol. We reply within one business day.

Talk to us