Residential proxies

Residential proxies route your requests through real consumer devices on ISP networks worldwide. Target sites see them as ordinary household traffic, making them the most resilient choice against anti-bot defenses.

At a glance

Type code	res
Delivery	Gateway, username-encoded
Endpoint	gate.helodata.io:7777
Billing	Pay per GB
Pool size	100M+ IPs
Geo targeting	Country, state, city, ASN
Session length	Rotating (per connection) or sticky (up to 30 min)
Protocols	HTTP, HTTPS, SOCKS5
Authentication	User+password or IP whitelist

When to use residential

• Sites with strong anti-bot defenses (e-commerce, ticketing, social platforms)
• Geo-restricted content that requires a real consumer IP in a specific country
• Ad verification and SERP tracking that must blend with real user traffic
• LLM data pipelines that need fresh, unblocked web pages

If your target is unprotected, Datacenter proxies (coming soon) are cheaper. If you need the same IP for hours or days, ISP proxies are a better fit.

Username grammar

helo_{username}-type-res-region-{region}[-state-{state}][-city-{city}][-asn-{asn}][-session-{session_id}-sesstime-{ttl}]

Full reference: Username format.

Five-second example

curl -x http://helo_s1a2b3c4d5e-type-res-region-us:[e-mail]:7777 \
     https://ipv4.icanhazip.com

On this page

• Quick start — first request in five minutes
• Authentication — password vs IP whitelist
• Endpoints & ports — host, port, TLS
• Locations — countries, states, cities
• Protocols — HTTP / HTTPS / SOCKS5
• Sessions & rotation — sticky vs rotating
• ASN targeting — pin a specific ISP
• Restricted targets — sites we don't route to
• Error definitions — what each status code means
• Statistics — dashboards and the traffic API