HTTP & SOCKS5

Aethyn exposes both protocols on dedicated ports. Same credentials, same targeting, different wire format. Pick whichever your client supports.

Endpoints

Each product has its own port pair, but the host is the same:

Premium Residential
  HTTP/HTTPS  →  proxy.aethyn.io:5499
  SOCKS5      →  proxy.aethyn.io:3499

Standard Residential
  HTTP/HTTPS  →  proxy.aethyn.io:2099
  SOCKS5      →  proxy.aethyn.io:1099

Use HTTP when

— You're scraping or hitting REST APIs
— Your client (Python requests, Node fetch, Go net/http) expects an HTTP proxy
— You want the simplest setup

import requests

proxy = "http://aethyn-XXXXX:PASS@proxy.aethyn.io:5499"
r = requests.get(url, proxies={"http": proxy, "https": proxy})

Use SOCKS5 when

— You're routing non-HTTP traffic (DNS, custom TCP)
— Your tooling (Playwright, headless browsers, scraping frameworks) expects SOCKS5
— You need full duplex transparency

# httpx with SOCKS5
import httpx

proxy = "socks5://aethyn-XXXXX:PASS@proxy.aethyn.io:3499"
async with httpx.AsyncClient(proxy=proxy) as client:
    r = await client.get(url)

HTTPS through HTTP

The HTTP port also handles HTTPS via the standard CONNECTverb. You don't need a separate port for TLS targets.