Common proxy ports
The ports proxies actually run on, what each one is, and how many free proxies answer on it right now. Every port links to its own live list.
| Port | What it is | Live now | |
|---|---|---|---|
| 8080HTTP alternate | The conventional alternate web port, used when port 80 is taken or requires privileges the software does not have. | 3,262 | View list |
| 999Compact alternate | A three-digit high port with no standard service attached. | 1,699 | View list |
| 3128Squid default | The default listening port of Squid, the most widely deployed open-source caching proxy. | 1,219 | View list |
| 1080SOCKS | The IANA-assigned port for the SOCKS protocol, used by both SOCKS4 and SOCKS5 since the specification was published. | 973 | View list |
| 3129Squid neighbour | The port directly above Squid's default, commonly used for a second Squid instance or an intercept listener. | 605 | View list |
| 80HTTP | The standard port for unencrypted web traffic; every browser assumes it when a URL carries no port. | 600 | View list |
| 8888HTTP alternate | A conventional alternate web port, notably the default of several debugging proxies and local web tools. | 439 | View list |
| 8081HTTP alternate | A spillover web port, typically chosen when 8080 is already occupied on the same machine. | 421 | View list |
| 4145SOCKS4 convention | Not an IANA assignment but a long-standing convention for SOCKS4 services, inherited from widely-circulated server builds. | 386 | View list |
| 5678SOCKS convention | A port with no meaningful IANA role that became a de-facto home for SOCKS services in public proxy lists. | 250 | View list |
| 1081SOCKS neighbour | The port directly above the SOCKS assignment, used for second instances or port-forwarded SOCKS services. | 245 | View list |
| 8118Privoxy default | The default port of Privoxy, a filtering web proxy often deployed in front of anonymity networks. | 233 | View list |
| 443HTTPS | The standard port for TLS-encrypted web traffic, and the one port effectively no firewall blocks outbound. | 192 | View list |
| 9999High alternate | A memorable high port with no reserved role, popular for ad-hoc services of every kind. | 159 | View list |
| 9090HTTP alternate | A common unprivileged web port, the default admin or web port of several server tools. | 149 | View list |
| 8000Development HTTP | A common unprivileged web port, the default of many development servers and lightweight HTTP daemons. | 138 | View list |
| 808Compact alternate | A three-digit echo of 8080 with no reserved role of its own. | 90 | View list |
| 10000Round high port | The first five-digit round number, conventionally the default of the Webmin admin panel among other tools. | 87 | View list |
| 8899HTTP alternate | A doubled-digit web port in the 8000 family, free of any standard assignment. | 52 | View list |
Other busy ports
Ports without a famous default service that still carry a real cluster of proxies, by live count.
What a proxy port is
If an IP address is a building, a port is a numbered door. A single machine exposes 65,536 of them, numbered 0 to 65535, and each can run a different service, which is how one server hosts a website on one port and accepts proxy connections on another. You connect to a proxy as an address and a port together, and the port is not optional: the same address on the wrong port reaches nothing at all.
Ports fall into three ranges. The well-known ports below 1024 are reserved for standard services and need elevated privileges to bind, which is why web traffic sits on 80 and 443 and why services people run casually tend to sit above it. The registered range up to 49151 is where most proxy software lives, 8080, 3128 and 1080 among it. The dynamic range above that is meant for short-lived outbound connections, though scanners and public lists drag a long tail of proxies up there too.
Which port a proxy uses is convention and habit rather than rule. Software ships with a default, operators pick memorable numbers, and public lists keep re-testing the ports they already know, so the busy ports stay busy. That feedback loop is most of what the counts above are measuring.
What the port tells you, and what it does not
A port number carries exactly one reliable piece of information: where to knock. It says nothing about whether an individual proxy is fast, private, still alive, or willing to relay to your destination. Those are properties of the address, measured per address, and no amount of reading the port will substitute for testing it.
It does carry a weak hint about provenance, which is worth knowing when you are reading a public list. 3128 is Squid's default, so entries on it are usually an open proxy left exposed rather than a service anyone meant to publish. 1080 is the traditional port for a SOCKS5 proxy. 8080 is the most common alternative HTTP proxy port. None of that is a guarantee, because a provider is free to listen wherever it likes.
The one inference you should never make is the protocol. A port does not tell you whether an endpoint speaks HTTP or SOCKS, and configuring a SOCKS endpoint as an HTTP proxy fails in a way that looks exactly like the proxy being dead. Take the protocol from the documentation, not from the number.
When the port is the problem
There is one failure mode that looks like a dead proxy and is not, and it is worth being able to recognise because the fix is completely different. Corporate networks, school networks, a good deal of public Wi-Fi, and many cloud security groups permit outbound connections only on a short list of expected ports, usually 80 and 443. A proxy listening on 1080 or 8080 is then unreachable from that network specifically, while working perfectly from anywhere else.
The diagnosis is quick. If a proxy answers from your phone on mobile data but not from the office, you are looking at outbound filtering between you and the proxy rather than a problem with the proxy itself. Nothing about the address, the credentials or the provider is wrong, and changing any of them will not help.
The fix is an endpoint on a port the network permits, which most providers can offer, rather than a different provider. It is also the reason to check this before concluding that a service is unreliable: an endpoint that fails from one network and succeeds from another is describing the network, not the endpoint.
How to test a port properly
Testing that a port is open and testing that a proxy works are two different checks, and conflating them is why free lists are full of entries that never worked. A TCP connection completing tells you a process is listening. It does not tell you the service speaks a proxy protocol, that it will relay to an arbitrary destination, that it does not require proxy authentication you do not have, or that it will still be there in an hour. This is precisely why a free proxy list assembled from port scanning alone is mostly dead entries.
The only test that answers the question you actually care about is a real request: send one through the endpoint to something that echoes back what it received, and read the answer. That single check settles whether it relays at all, which exit node you got, which country it geolocates to, and whether it added an X-Forwarded-For header naming you. Everything else is inference.
This is also the order to debug in. Test the endpoint directly first, because if it returns the right country and your application does not, the problem is in the application's configuration and no amount of changing proxies will fix it.
Questions about proxy ports
What port do proxies use?
There is no single proxy port, but a handful dominate. HTTP proxies cluster on 8080, 3128 and 80; SOCKS proxies on 1080 and 4145; and anything can appear on 443 to travel through strict firewalls. The table above shows the live count on each, which is the honest answer to which ports are busiest right now.
What is the default proxy port?
It depends on the software. Squid, the most common open-source proxy, defaults to 3128. Proxy tools that cannot use privileged ports default to 8080. SOCKS servers default to 1080. A proxy can be configured to listen anywhere, so the default is a convention of the software, not a rule of the protocol.
Why do proxies use port 8080 so often?
Ports below 1024 need elevated privileges to bind, so proxy software that runs as an ordinary user reaches for 8080, the conventional alternate web port. That, plus scanners checking it first, has made 8080 the single most published proxy port there is.
Is the port part of connecting to a proxy?
Yes. You connect to a proxy as an address and a port together, like 203.0.113.9:8080. The same address without the right port points at nothing, which is why every entry in a proxy list carries both.
Does the port tell me if a proxy is safe or fast?
No. The port is only which door the service listens behind. It says nothing about speed, anonymity or whether the proxy is still alive, all of which we measure per address on its own page. A proxy on a common port is not safer than one on an unusual port; it is just easier to find.