Port 10384 — The Unassigned Port

What This Port Is

Port 10384 is a registered port — meaning it falls in the range 1024–49151 — but it has no official IANA service assignment. No RFC defines it. No major application claims it.

The Port Ranges, Explained

The Internet divides 65,535 possible ports into three regions:¹

• Well-Known Ports (0–1023): System services and critical protocols. SSH at 22, HTTP at 80. These are standardized globally.
• Registered Ports (1024–49151): For applications that need a stable port number. They can register with IANA and get one assigned. Port 10384 lives here.
• Dynamic/Ephemeral Ports (49152–65535): Temporary, assigned on-the-fly by operating systems. Usually invisible to users.

Port 10384 is in the middle region: respectable, assigned-capable, but unclaimed.

Is It Actually Used?

Not officially. No major service, library, or standard has registered it with IANA.² You won't find it in the official port registry.

This doesn't mean nothing runs there — private applications, internal tools, or misconfigured services might be listening on 10384 on any given machine. But there's no global convention saying "when you see 10384, expect X protocol."

Why Unassigned Ports Matter

The unassigned ports are the honest ones. They tell the truth about the Internet: we have more space than we have names for. We have more potential than we have standardization.

They also matter practically. If a port is unassigned, you can use it for internal services without fear of collision. Some administrators prefer this. "I don't want to fight for an official IANA registration. I just need something to listen on port 10384 inside my network."

How to Check What's Listening on 10384

On your local machine:

# macOS/Linux
lsof -i :10384
netstat -tulpn | grep 10384
ss -tulpn | grep 10384

# Windows (PowerShell as admin)
netstat -ano | findstr :10384
Get-NetTCPConnection -LocalPort 10384

If nothing appears, port 10384 is dark. Empty. Waiting.