Port
A numbered channel on an IP address that directs traffic to a specific service, such as the port your proxy listens on.
If an IP address is a building, a port is a numbered door in it. One address exposes 65,536 of them, numbered 0 to 65535, and each can run a different service, which is how a single machine serves web pages on one port while accepting proxy connections on another. That is why a proxy is always given as an address AND a port: the address finds the machine, the port finds the service.
The numbers carry conventions rather than rules, and it helps to know the ones you will actually meet. 80 is plain HTTP and 443 is HTTPS. 1080 is the traditional SOCKS port. 3128 is Squid's default and turns up constantly on public proxy lists because so many misconfigured Squid installations are exposed. 8080 is the most common alternative HTTP proxy port. Anything below 1024 is privileged and requires elevated permissions to bind, which is why services people run casually tend to sit above it.
But every one of those is a convention a provider is free to ignore, and many do. A proxy listens wherever it was configured to listen, and providers routinely separate services or pools by port on the same host, so one hostname might answer HTTP on one number and SOCKS on another. Never infer the protocol from the port; take it from the documentation.
The practical trap is outbound filtering, and it produces a failure that looks like a dead proxy when the proxy is perfectly healthy. Corporate networks, school networks, some hotel and public Wi-Fi, and a good many cloud security groups permit outbound traffic 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 fine from anywhere else.
That distinction is diagnosable, which is what makes it worth knowing. If a proxy answers from your phone on mobile data but not from the office network, you are almost certainly looking at an outbound port restriction rather than a proxy problem, and the fix is an endpoint on a permitted port rather than a different provider.
Frequently asked questions
What port do proxies usually run on?
There is no single answer, only conventions. 1080 is traditional for SOCKS, 3128 is Squid's default and appears constantly on public lists, and 8080 is the most common alternative HTTP proxy port. Providers frequently choose their own, and the same host can serve different protocols or different pools on different ports, so take the number from the provider's documentation rather than assuming.
Why can I connect to my proxy from home but not from work?
Almost always outbound port filtering on the restrictive network. Many corporate, school and public networks allow outbound connections only on expected ports such as 80 and 443, so a proxy listening on 1080 or 8080 is unreachable from there while working perfectly elsewhere. The proxy is fine; the network between you and it is not letting you out.
Does the port number affect speed or anonymity?
Not by itself. A port is a routing label, and the number has no bearing on throughput or on what your requests reveal. Anonymity is decided by the protocol and by which headers the proxy adds or strips, and speed is decided by the path and the infrastructure. The only way a port choice affects you is by being blocked somewhere between you and the proxy.
What does port 3128 mean on a free proxy list?
It usually indicates a Squid caching proxy left open, since 3128 is Squid's default. That is worth knowing because it tells you something about the entry's origin: these are typically misconfigured installations rather than services intended for public use, which is exactly the profile of an open proxy nobody is accountable for.
Back to the full glossary.