Ports & SuperPorts

A proxy port is the numbered endpoint your client connects to on the gateway, and it determines which connection slot (and, with SuperPorts, which geo and session settings) your request uses. ColdProxy gateways assign connections using ports in the 30000–34999 range. Beyond plain port assignment, SuperPorts let you bind geo-targeting and a sticky duration to specific port ranges at the plan level, so requests through those ports carry those settings automatically, with no per-request username tags required. This page explains which proxy port to connect on, how the range works, and how to set the right one.

#Ports

#The proxy server port range

All three protocols (HTTP, HTTPS, SOCKS5) share the same proxy server port range: 30000 to 34999. There is no separate range per protocol.

When you use gw-2312.coldproxy.com:30000 in an example, 30000 is just a convenient starting point. Any port in your plan's allocation works; ColdProxy plans are currently provisioned with the standard full 30000–34999 range, so in practice every port in the range answers today.

#Ports per plan

Each plan can be provisioned with 1 to 5,000 unique ports within the 30000–34999 range. The 5,000 figure is the configurable ceiling, not a default. Provision the number of ports your workload actually needs: a light scraper might need 10 ports; a high-concurrency pipeline might need several thousand.

Both User:Pass and IP Authentication draw from this range; your service's exact port range for each method is returned by the plan API's info action (user_ports and ip_auth_ports).

# Port 30000 — the default example port
curl -x "http://USERNAME:PASSWORD@gw-2312.coldproxy.com:30000" \
  "https://api.vipv6proxy.com/api/checker/my-ip"

# Port 31500 — equally valid
curl -x "http://USERNAME:PASSWORD@gw-2312.coldproxy.com:31500" \
  "https://api.vipv6proxy.com/api/checker/my-ip"

#SuperPorts

#What SuperPorts do

SuperPorts bind a set of settings (country, state, city, ISP, and sticky duration) to a specific port range at the plan level. Any request through a port in that range automatically uses those settings; setting a sticky duration makes the whole range sticky. No per-request username tags are needed.

This is the primary way to apply geo-targeting and sticky sessions to IP-authenticated traffic. Because IP-authenticated requests carry no username, they cannot use username tags for geo or session control. SuperPorts fill that gap by encoding the behavior in the port itself.

#Worked example

Suppose you configure a SuperPort rule:

Any request through a port in 30000–31000 automatically exits from a US IP and holds that IP for 10 minutes:

# IP-authenticated — no credentials in the string, geo/session from SuperPort
# Use the IP:PORT form shown in your client area
curl -x "http://203.0.113.10:30000" \
  "https://api.vipv6proxy.com/api/checker/my-ip"

# User:Pass — same SuperPort range; sticky session inherited automatically
curl -x "http://USERNAME:PASSWORD@gw-2312.coldproxy.com:30000" \
  "https://api.vipv6proxy.com/api/checker/my-ip"

import requests

# IP-authenticated traffic through a SuperPort-bound range
# Use the IP:PORT form from your client area
proxy = "http://203.0.113.10:30000"
proxies = {"http": proxy, "https": proxy}

for _ in range(5):
    # All five requests exit from the same US IP (10-minute sticky)
    print(requests.get("https://api.vipv6proxy.com/api/checker/my-ip", proxies=proxies, timeout=30).json())

#Username tags override SuperPort defaults

SuperPort settings are plan-level defaults. When both apply, username tags take precedence over SuperPort bindings. This means you can set a sensible plan-wide default with SuperPorts and override it per request with username tags on User:Pass traffic.

# SuperPort on ports 30000-31000 defaults to US + 10-minute sticky
# This username tag overrides the country to Germany for this specific request
curl -x "http://user-country-de:PASSWORD@gw-2312.coldproxy.com:30000" \
  "https://api.vipv6proxy.com/api/checker/my-ip"

#SuperPorts and IP Authentication

SuperPorts are the standard geo-targeting path for IP-authenticated users. Without SuperPorts, IP-authenticated traffic defaults to Worldwide routing. With SuperPorts you can assign any port range to a specific country (or state, city, or ISP) and a sticky duration, giving IP-auth users the same geo and session control that User:Pass users get through username tags.

#SuperPorts API

SuperPort bindings are managed through the plan API. The API lets you list, create, and delete port-range rules without going through the client area UI, useful for automating multi-region fleet provisioning; to change a rule, delete it and add the replacement. See the Customer Plan API reference for the available commands.

#Bulk removal

When you need to clear a plan's SuperPorts, you can remove them all in a single action (a bulk removal from the client area or the API) instead of deleting each port-range rule one by one. The same bulk removal is available for authorized IPs.

#Sticky duration reference

Sticky duration limits depend on the product, not the port or SuperPort configuration:

#Next steps

• Authentication — User:Pass and IP whitelisting, and how to use both together.
• Username Tag Scheme — per-request geo and session control for User:Pass traffic.
• Sessions: Sticky vs Rotating — the rules behind sticky and rotating IP behavior.
• Geo-targeting with proxies
• Glossary: Geo-targeting · Sticky session · Port