What This Port Is
Port 10350 is officially unassigned. It has no entry in the IANA Service Name and Transport Protocol Port Number Registry. This is not a bug or an oversight—it's how the port system is designed.
Port Range: Registered Ports (1024-49151)
Port 10350 lives in the registered port range, which means it exists between the well-known ports (0-1023, officially assigned to standard protocols like HTTP, SMTP, SSH) and the ephemeral ports (49152-65535, dynamically assigned for temporary connections).
The registered range is where application developers can request official assignments from IANA for new protocols or services. But not every application does. Many just pick a port that seems unlikely to conflict and move on.
Known Unofficial Uses
Port 10350 has been claimed by at least two open-source projects:
Tilt 1 — A local development tool for Kubernetes that runs a web server on port 10350 by default. This server hosts a React dashboard showing the state of your development environment. The port choice is arbitrary but documented; users can override it with --port or the TILT_PORT environment variable.
kapp-controller 2 — A Kubernetes deployment tool that uses port 10350 as its default API port. The problem: major hosted Kubernetes platforms (GKE, EKS) often block this port by default, requiring users to reconfigure or request exceptions.
Neither of these tools registered the port with IANA. They simply chose it because it seemed safe and memorable.
Why Unassigned Ports Matter
The vast majority of running services on the Internet use either:
- Well-known ports (everyone agrees on them)
- Ephemeral ports (temporary, chosen on the fly)
- Unassigned registered ports (chosen by individual applications)
Port 10350 represents the third category: the practical middle ground where developers build without needing a formal spec or central authority. This works most of the time because port collisions are rare. When they do happen, it's a local problem, not a protocol-wide catastrophe.
How to Check What's Listening
To see if something is listening on port 10350 on your machine:
On Linux or macOS:
On Windows:
On any system (with netcat):
If port 10350 is open and you don't recognize the application, check:
- Your running development tools (Tilt, Kubernetes-related software)
- Docker containers or VMs
- Any recent installations that might customize their ports
The Unassigned Port Ecosystem
Thousands of ports in the registered range are unassigned and unused. They exist as quiet optionality—available when someone needs them, claimed when they do. Port 10350 is one of the honest ones: it's claimed by real tools, documented in their code, and serves a genuine purpose.
The port system works because most applications are polite about choosing ports they're unlikely to need forever. We all implicitly agree that if you're building something that doesn't need global coordination, pick something high and move on.
Port 10350 is the Internet being pragmatic.
Questa pagina è stata utile?