Puerto de proxy
El número de puerto de red en un servidor proxy al que se conecta tu cliente, que determina el protocolo y el gateway que usas.
Un puerto de proxy es el punto numerado de un servidor proxy al que se conecta tu cliente, escrito como la segunda mitad de host:port. Cuando configuras un proxy como 123.45.67.89:8080, el 8080 es el puerto. El puerto le indica al servidor proxy qué servicio -y a menudo qué protocolo- quieres usar.
Los distintos puertos suelen corresponder a distintos protocolos o comportamientos. Un proveedor puede exponer HTTP en un puerto y SOCKS5 en otro para el mismo pool de IP. Los puertos también pueden codificar el comportamiento de rotación - por ejemplo, un puerto para rotación por solicitud y otro para sesiones sticky - de modo que elegir el puerto selecciona cómo se asignan las IPs.
Convenciones de puertos comunes que verás: 8080, 3128 y 8000 para proxies HTTP y 1080 para proxies SOCKS, aunque los proveedores asignan los puertos que eligen. Usa siempre el puerto exacto del panel de tu proveedor; conectarte al puerto equivocado es una causa frecuente de errores de "proxy no responde".
Si un proxy da timeout, verificar el puerto es una de las primeras comprobaciones: un proxy puede anunciar SOCKS5 en un puerto que en realidad no es accesible, o esperar HTTP en un puerto distinto. Un verificador de proxy que prueba ambos protocolos ayuda a identificar qué combinación de puerto y protocolo funciona de verdad.
What the number after the colon actually decides
A proxy address has two parts and people usually think about the wrong one. The IP tells your client which machine to talk to. The port tells that machine which service should answer. One host can run twenty proxy services on twenty ports, and each can speak a different protocol, apply different rules and belong to a different customer.
Ports carry no meaning of their own. Nothing in the TCP standard makes 8080 an HTTP proxy or 1080 a SOCKS proxy. Those are conventions that stuck: 8080 because it reads as an alternative to 80, 3128 because Squid picked it, 1080 because the SOCKS specification used it in examples. A provider is free to put an HTTP proxy on 41209, and many do, precisely because scanners look at the conventional numbers first.
What the port does decide is which protocol the service on the other end expects. Point an HTTP client at a SOCKS port and the handshake fails immediately, usually as a connection reset or an unreadable response rather than a clear error. This is the single most common cause of setup problems that look mysterious and are not.
Ports below 1024 are privileged on Unix systems and are also the ones network administrators watch. Corporate firewalls often allow 80 and 443 and block everything else outbound, which is why proxy services that need to work from inside offices sometimes offer an alternative port on 443.
Which ports we use and why
We run three different port schemes because the three products work differently underneath:
Ports by product
Residential (rotating and sticky)
proxy.sotaproxy.com:10000 HTTP and SOCKS5 on the same port
Static addresses (ISP, datacenter, IPv6)
your-ip:50100 HTTP
your-ip:50101 SOCKS5
Mobile modems
ports differ per modem, take them from the dashboard- On residential, one port serves both protocols. The service reads the first bytes of your connection and works out whether it is an HTTP request or a SOCKS handshake, so you do not pick a port, you pick a scheme in your client.
- On static addresses SOCKS5 always sits one number above HTTP. If HTTP works and SOCKS5 does not, check that you added the one rather than assuming a different port entirely.
- Mobile is the exception: modems come from the upstream network with their own port assignments, so hardcoding a number that worked for one modem will break on the next.
- Test the port before blaming credentials. A 407 means the port was right and the login was wrong. A connection reset usually means the opposite.
Where people get ports wrong
Assuming a port implies a protocol
8080 is not guaranteed to be HTTP anywhere. Read the provider documentation instead of guessing from the number, because a wrong guess produces errors that look like network faults.
Blaming the proxy for a firewall
If a port works from home and fails at the office, the proxy is fine and the outbound rule is not. Test with curl from both networks before opening a ticket.
Reusing a port across products
Our residential endpoint answers on 10000 and our static addresses answer on 50100. Copying a port from one setup into another is a frequent and confusing mistake.
Thinking a port change hides you
Running a proxy on an unusual port does nothing for anonymity. What the target site sees is the exit address, not the port your client connected to.
Ports you will actually meet
Numbers below are conventions, not rules. Nothing in TCP makes a port mean a protocol, and every row here can be moved by whoever runs the service.
| Port | Usually runs | Where the convention came from |
|---|---|---|
| 80 | HTTP proxy, plain | The web port itself. Survives firewalls that allow almost nothing else. |
| 443 | HTTP proxy over TLS | The HTTPS port. Providers put proxies here so corporate networks let them out. |
| 1080 | SOCKS4 and SOCKS5 | The SOCKS specification used it in its examples and it stuck. |
| 3128 | HTTP proxy | Squid ships with this as its default listening port. |
| 8080 | HTTP proxy | Reads as an alternative to 80. The single most common proxy port anywhere. |
| 8118 | HTTP proxy | Privoxy default. |
| 9050 | SOCKS5 | The Tor daemon default. 9150 is the one Tor Browser uses. |
| 10000-10999 | Our residential gateway | Every port in the range answers both HTTP and SOCKS5. |
| 50100 / 50101 | Our static addresses | HTTP on the first, SOCKS5 one number above. |
We checked the range ourselves on 12.09.2026: 10000, 10001, 10500 and 10999 all answer an HTTP request with 407 and complete a SOCKS5 handshake, while 11000 answers nothing. So on residential the port is not what selects the protocol, the scheme in your client is.
Questions people actually type
What is a proxy port?
The number after the colon in host:port. The address says which machine to reach, the port says which service on that machine should answer. One server can run many proxy services, each on its own port, each with different rules.
What is the proxy port number I should use?
The one your provider gives you, not one you guessed from a list. With us it is 10000 for residential and 50100 for static addresses, and both come with the credentials. A wrong port produces a connection reset, which looks like a network fault and is not.
Does the port decide whether it is HTTP or SOCKS5?
Not by itself. It decides which service answers, and that service decides which protocols it speaks. Our residential gateway speaks both on the same port: you choose by writing http:// or socks5:// in your client. On our static addresses the two protocols do sit on separate ports, 50100 and 50101.
How do I find my proxy port?
Take it from wherever the proxy came from: the provider dashboard for a bought proxy, or the system settings for one your network imposes. On Windows that is Settings, Network and Internet, Proxy. On macOS it is System Settings, Network, the active interface, Proxies. In Chrome and Edge the proxy settings open the same system dialogue rather than a browser one.
Why does SOCKS5 fail on a port where HTTP works?
Because that service only speaks HTTP. The failure usually arrives as a connection reset or unreadable response rather than a clear message, which is why it gets mistaken for a broken proxy. Check the provider documentation for which protocol the port serves before changing anything else.
Does an unusual port make me harder to detect?
No. The site you visit sees the exit address and the traffic, never the port your client dialled. Running a proxy on 41209 instead of 8080 hides it from casual scanners, not from the target.
Términos relacionados
Ver esto en práctica
¿Listo para usar puerto de proxy?
SotaProxy te da acceso a proxies residenciales rotativos, móviles, de centro de datos e ISP. Sin compromiso mínimo.
Empezar