Residential IPv6 Connection Reference
Residential IPv6 uses dedicated, subscription-specific endpoints on ISP-class IPv6 space. Copy the exact encrypted endpoints and credentials shown for your subscription in the dashboard; the shared Residential IPv4 hostname and ports do not apply.
Connection contract
Section titled “Connection contract”| Setting | Value |
|---|---|
| Address family | IPv6 exits from ISP-class address space |
| HTTP proxy | https://YOUR_ASSIGNED_HOST:443 |
| SOCKS proxy | socks5+tls://YOUR_ASSIGNED_HOST:YOUR_ASSIGNED_PORT |
| Authentication | The credentials or IP allowlist displayed for the subscription |
| Endpoint source | Dashboard subscription details |
| Direct public UDP associate | Not supported |
Plain SOCKS5 clients cannot connect directly to the encrypted SOCKS endpoint. Use a supported TLS-capable client or a local adapter/TLS wrapper as described in How to Connect.
Compatibility first
Section titled “Compatibility first”Confirm that the destination, DNS path, client library, and runtime support IPv6 before scaling. An IPv4-only destination cannot use an IPv6 exit merely because the client can reach the proxy gateway.
Use a small representative request set to verify:
- The destination resolves to and accepts IPv6.
- The client uses the encrypted endpoint and issued credentials.
- The observed exit matches the expected ISP-class route.
- The subscription behavior fits the target and retry policy.