1. Ports
  2. Port 2115

Port 2115 sits in the registered port range (1024-49151), which IANA manages for applications that need a documented, stable port number. Unlike the well-known ports below 1024, you don't need superuser privileges to bind here. Unlike the ephemeral ports above 49151, this range is meant to be claimed and registered.

Port 2115 wasn't. 1

The "kdm" Mystery

Search port databases and you'll find port 2115 listed as kdm — Key Distribution Manager, described as an SSH key management service for Unix environments. The attribution appears across multiple reference sites, cited confidently.

IANA's official Service Name and Transport Protocol Port Number Registry lists 2115 as unassigned. 1

No RFC. No official registration. The "kdm" label appears to be a ghost — a designation that circulated through secondary sources and got repeated until it looked authoritative. This happens more than you'd expect in the port world: informal documentation propagates, databases copy each other, and an unofficial association acquires the appearance of fact.

Don't rely on the "kdm" label for anything. If you see traffic on port 2115 and expect it to be Key Distribution Manager, verify it. The name has no official backing.

What This Range Means

The registered port range (1024-49151) works like a reservation system. An application developer submits a request to IANA, documents what their protocol does, and gets a dedicated port number that won't collide with other registered services. 2

This matters because two applications picking the same port independently would break anyone trying to run both. Registration is the coordination mechanism.

Port 2115 went through none of that process. It's open space — available, but unclaimed.

What Might Actually Be Listening

Unassigned ports get used all the time, just without ceremony. You might find:

  • Custom internal services that picked a number not already taken
  • Development servers or test environments
  • Software that chose this port arbitrarily and never registered it

The only way to know what's actually on port 2115 on a specific machine is to look.

How to Check What's Listening

On Linux/macOS:

ss -tlnp | grep 2115
# or
lsof -i :2115

On Windows:

netstat -ano | findstr :2115

Across the network (with nmap):

nmap -sV -p 2115 <target-ip>

The -sV flag asks nmap to probe the service and identify what's actually running, rather than guessing from the port number alone. That probe is worth running — especially here, where the port number tells you almost nothing.

Why Unassigned Ports Matter

The registered port space has 48,128 slots. A meaningful fraction are unassigned, and that's fine — the alternative would be forcing every application to pile into the same small set of official ports.

Unassigned ports are the Internet's rough draft. Some will eventually get formal registrations. Most will be used, reused, and abandoned without anyone keeping records. Port 2115 is among them: a number in the middle of a large namespace, waiting for something to make a permanent home here.

Frequently Asked Questions

此頁面對您有幫助嗎?

😔
🤨
😃