What Port 10443 Is
Port 10443 isn't assigned to anything official. It sits in the registered port range (1024–49151), which means IANA has kept it available for whoever asks, but nobody has asked yet. Or more accurately: nobody who mattered enough to get it officially registered.
In practice, it's everywhere in enterprise networks.
The Unofficial Story
Port 10443 is the escape hatch when port 443 is locked down.
Broadcom DLP (Data Loss Prevention) uses it for endpoint agents to phone home securely. FortiClient uses it for management server communication. VMware vCenter listens there. Traefik reverse proxies land on it. Security teams, VPN vendors, and network appliances have collectively decided: when you need a second HTTPS channel and can't fight for port 443, use 10443.
It's the port equivalent of double-parking. Not technically yours, but nobody's objecting.
Why This Port Gets Used
Three reasons:
-
Port 443 is taken — Most networks run a web server or VPN on the standard HTTPS port. Management consoles need somewhere else to talk.
-
Firewall rules can isolate it — Security teams can allow internal traffic on 10443 while blocking 443 to the Internet, or vice versa. The port number is a traffic control mechanism.
-
Avoiding root privileges — Ports below 1024 require root on Unix systems. 10443 is high enough to run as a regular user, making it attractive for containerized applications and security software that wants to avoid running as root.
How to Check What's Listening
On Linux/Mac:
On Windows:
If something's listening, it's probably one of these:
- A Fortinet security tool
- Broadcom DLP Endpoint Server
- VMware management console
- Docker/container orchestration reverse proxy
- Corporate VPN concentrator
Don't be surprised if it's something you didn't install yourself. Enterprise security software loves this port.
The Bigger Picture
Port 10443 is a window into how the Internet actually works versus how it's supposed to work.
IANA maintains the official registry. RFC 6335 defines the procedures. But the real port allocation happens in thousands of corporate networks, Docker containers, and cloud deployments where engineers need to route traffic and just pick a number.
Port 10443 has no RFC. No committee assigned it. It's just where people put the backup HTTPS server. And because thousands of organizations did exactly the same thing independently, it became semi-official through collective action.
This is how standards emerge outside the standards process: repetition becomes convention becomes expectation. Ports don't mean what IANA says they mean. Ports mean what the network does with them.
Related Ports
- Port 443 — The official HTTPS port. The one everyone fights over.
- Port 8443 — Another HTTPS alternative, even more common for development and testing.
- Port 9443 — Yet another variant, preferred by some vendors for administrative interfaces.
- Port 10080 — The HTTP companion to 10443, occasionally seen alongside it.
The presence of all these variants tells you something: the port system assumed one web server per machine. It never anticipated containerization, VPN concentrators, security appliances, or networks complex enough to need five different HTTPS channels.
Cette page vous a-t-elle été utile ?