Backconnect Proxy

A backconnect proxy presents one fixed gateway address to your client while, behind the scenes, routing each connection through a large pool of exit IPs. You connect to the single endpoint and the provider handles rotation for you, so you never manage individual addresses. It is the delivery mechanism most rotating proxy services use: one entry point, many exits. The design hides pool complexity behind a stable front door.

A backconnect client uses one gateway; its rotation policy selects an exit IP per request, session or time interval. This can distribute scraping traffic, but does not override a destination's rate limits or access rules. Session continuity depends on sticky-session support, assignment duration and failures; rotation does not guarantee a different address for every request.

Authenticated SOCKS5 (1080) and HTTP (3128) use the configured endpoint. Proxy credentials remain required when you choose another available exit. s4m has selectable public exit configurations. Use the endpoint or profile issued for the protocol and location selected in your account. Selecting an exit does not automatically rotate every request. Configure your client for the issued endpoints, preserve stateful sessions and respect applicable limits. The free list contains separate third-party endpoints. Past checks do not guarantee availability; validate candidates before use. Related topics: SOCKS5, HTTP, dedicated IP, public list, proxy plans.