Residential IPv4 Connection Reference
TrueProxies exposes Residential IPv4 through Unlimited and GB-Based billing products. This page documents the shared connection contract; use the Unlimited and GB-Based product pages for current commercial terms.
Connection contract
Section titled “Connection contract”| Setting | Value |
|---|---|
| Address family | IPv4 exits from residential ISP networks |
| HTTP CONNECT endpoint | http://YOUR_HOST:YOUR_HTTP_PORT |
| SOCKS5 endpoint | socks5://YOUR_HOST:YOUR_SOCKS_PORT |
| Authentication | Username/password, or IP allowlisting when the dashboard exposes it |
| Targeting | Country, city, region, continent, ASN, ZIP, ISP |
| Sessions | Sticky by session id, with a lifetime you set |
Targeting can be written on the username or on the password, and the two are equivalent. The full option list, with the accepted values and the vendor spellings we also accept, is in How to Connect — kept in one place so it cannot drift from what the proxies actually honour.
Choose a session mode
Section titled “Choose a session mode”- Send no session for normal rotation.
rotateis accepted if an integration insists on naming it, and changes nothing — rotation is already the default. - Send a session id when a login, cart, or multi-page flow needs the same exit,
and set
lifetimeto how long you need it. - Keep a session id only for work that needs continuity. Reusing one identifier across unrelated jobs holds them all on a single IP.
Destination limit
Section titled “Destination limit”Residential IPv4 cannot reach IPv6-only destination hosts. Use a destination with an IPv4 address, or choose an IPv6 product whose assigned endpoint and exit match the job.