Protocols

Every plan supports HTTP, HTTPS, SOCKS5. The protocol is the language your application speaks to the proxy. It is independent of the website you visit: an HTTP proxy connection can load https:// sites, and the encryption stays end to end.

Which protocol should I use?Copy Anchor Link

Sticky ports (10000–20000) accept every protocol. See Endpoints and ports.

How HTTPS works through the proxyCopy Anchor Link

For an https:// URL, your client sends CONNECT example.com:443 to the proxy. The proxy opens a TCP connection to the site and relays bytes in both directions. Your client then negotiates TLS directly with the website, so:

• The proxy sees which host you connect to, but not the pages, headers or data.
• Certificates are the website's own, so certificate checks work normally.

You do not need any special setting for HTTPS: use the http:// proxy URL and request an https:// address.

SOCKS5Copy Anchor Link

SOCKS5 relays raw TCP connections, so it works for protocols other than HTTP too. Use the socks5h:// scheme where your client supports it: the h makes the proxy resolve host names, so DNS lookups happen in the proxy's location and do not leak from your machine. With socks5://, your machine resolves the name and sends the proxy an IP address.

curlCopy Anchor Link

curl -x "socks5h://USERNAME:PASSWORD@HOST:824" https://api.ipify.org

PythonCopy Anchor Link

# pip install "requests[socks]"
import requests

proxy = "socks5h://USERNAME:PASSWORD@HOST:824"
response = requests.get(
    "https://api.ipify.org",
    proxies={"http": proxy, "https": proxy},
    timeout=30,
)
print(response.text)

Node.jsCopy Anchor Link

// npm install socks-proxy-agent
import https from 'node:https';
import { SocksProxyAgent } from 'socks-proxy-agent';

const agent = new SocksProxyAgent('socks5h://USERNAME:PASSWORD@HOST:824');
https.get('https://api.ipify.org', { agent }, (res) => {
  res.on('data', (chunk) => process.stdout.write(chunk));
});

Is the connection to the proxy encrypted?Copy Anchor Link

No. Neither HTTP proxies nor SOCKS5 encrypt the connection between your application and the gateway, so the proxy username and password travel in a form that anyone on that network path could read. Your traffic to https:// websites stays encrypted end to end.

On networks you do not trust, use an IP allowlist instead of a password, and reset the password from the dashboard if you think it has leaked.