Port 10144 — Unassigned Registered Port

What Range Is This?

Port 10144 sits in the registered ports range: 1024–49151. ¹ These are the ports where anyone can claim a service by registering with IANA. They don't require administrative privileges to bind to (unlike 0–1023, which do). This makes the registered range the natural home for applications: databases, messaging systems, custom services, anything that needs a stable port but doesn't have the administrative weight to claim a well-known port.

Official Status

Port 10144 has no official IANA registration. ² It exists in the registry as a possibility, nothing more. This isn't unusual—the vast majority of registered ports go unclaimed. The registered range is enormous (48,128 ports), and only a fraction bear official assignments.

Known Unofficial Uses

The main trace of port 10144 in the wild comes from a Nessus vulnerability detection plugin. ³ The plugin, titled "Microsoft SQL Server TCP/IP Listener Detection," suggests that some SQL Server installations may be configured to listen on this port. However, this is not a standard SQL Server port—1433 is the default for the default instance. ⁴ If you find MSSQL on 10144, it means someone deliberately configured it there, choosing a non-standard port for whatever reason (security through obscurity, perhaps, though that's generally a bad reason).

Beyond that mention, port 10144 appears nowhere in standard port lists. No application claims it as home. No protocol defines it.

Why Unassigned Ports Matter

The existence of unassigned ports is the Internet's safety valve. They're the reason new applications don't deadlock waiting for an IANA allocation. An engineer can start a database, choose 10144 (or any unclaimed registered port), and it works. The system allows this because 48,000+ ports is abundance. Scarcity only exists at the extremes—the well-known ports that everyone fights over.

Unassigned ports also represent a kind of symmetry: if someone needed port 10144 badly enough to register it, it would exist. The fact that it doesn't means no major standard relies on it. No protocol was born from desperation to use this specific number.

Checking What's Listening

If you suspect something is using port 10144 on your system:

On Linux/macOS:

lsof -i :10144          # Which process is using this port
ss -tlnp | grep 10144   # Show listening socket details
netstat -tlnp | grep 10144  # Alternative (less reliable)

On Windows:

netstat -ano | findstr :10144
# Then check the PID in Task Manager to identify the process

Universally:

curl -v telnet://localhost:10144  # Does anything respond?

The Larger Picture

Port 10144 is not special. It's one of 48,000 that nobody owns. The reason it matters is precisely that reason—it's a reminder that the port system is designed with headroom, with space for the unexpected. Not every number needs a master. Some ports exist to be available.