Proxy Port Numbers: Common Ports and Which One to Use

Proxy port

A proxy port is the TCP port on which a proxy listens; providers usually run one port per protocol on the same hostname, for example 9000 for HTTP(S) and 9001 for SOCKS5, and sometimes dedicate port ranges to sticky sessions or countries. The port does not change the exit or the price; it only decides which protocol the client speaks to the gateway.

3 min read Also called gateway port Updated Oct 15, 2026

Two conventions#

One port per protocol, parameters in the username (HodlProxy, several others): simplest to configure, unlimited sessions.
Port ranges: each port maps to a fixed session or location (port 10001 = session 1…). Works with tools that cannot edit usernames, but caps the number of parallel sessions to the size of the range.

Ports on dedicated addresses#

Static ISP and datacenter addresses are delivered as ip:port with their own ports for HTTP and SOCKS5, distinct from the gateway ports; a list may therefore mix two port numbers per address.

Common proxy ports#

Port	Usually means	Notes
80	HTTP proxy on the standard web port	Rare for commercial proxies; often a transparent proxy
8080	HTTP proxy (alternative HTTP port)	The most common default for HTTP proxies and appliances
3128	Squid HTTP proxy	Squid's default; common in corporate networks
8888	HTTP proxy or debugging proxy	Used by local tools such as traffic inspectors
1080	SOCKS proxy	The registered SOCKS port
9050	Tor SOCKS port	Local Tor client, not a commercial proxy
9000 / 9001	HodlProxy gateways	HTTP(S) on 9000, SOCKS5 on 9001, for res. and mob.
8000 / 8001	HodlProxy dedicated addresses	HTTP(S) on 8000, SOCKS5 on 8001

Which port should you use?#

The one your provider assigns for the protocol your tool speaks. The port does not change the exit, the country or the price; it only decides how your client talks to the proxy. Speaking HTTP to a SOCKS port, or the reverse, fails immediately with a protocol error or a closed connection.

Troubleshooting a proxy port#

Connection refused: wrong host or port, or the port is closed for your source address.
Timeout: a firewall on your side blocks outbound connections to non-standard ports; corporate and some hotel networks do.
Garbled reply or immediate close: protocol mismatch between the client setting (HTTP or SOCKS5) and the port.
407: the port is right and the proxy answered; the credentials are the problem (see HTTP 407).

Check that a proxy port is reachable

# TCP reachability
nc -vz res.hodlproxy.com 9000

# Full test through the port, with verbose output
curl -v -x http://USER:PASS@res.hodlproxy.com:9000 https://api.ipify.org

How it works at HodlProxy#

HodlProxy uses port 9000 (HTTP/S) and 9001 (SOCKS5) on both gateways, and ports 8000 (HTTP/S) and 8001 (SOCKS5) on every dedicated address. Sessions are chosen in the username, so there is no port range to manage.

Questions people ask#

What port does an HTTP proxy use?

There is no fixed one: 8080 and 3128 are the most common defaults, and commercial providers pick their own. HodlProxy uses 9000 on its gateways and 8000 on dedicated addresses.

What port does a SOCKS5 proxy use?

Port 1080 by convention; HodlProxy uses 9001 on gateways and 8001 on dedicated addresses.

Does the proxy port affect my IP or location?

Not at HodlProxy: the exit and its location are chosen in the username, so one port serves every country and session. Some providers do map ports to sessions or countries instead.

Why does my proxy port time out?

Most often a firewall on your own network blocks outbound connections to that port. Test from another network or a server; if it works there, ask your network administrator to allow it.

Proxies

Menu