Port 2384: Technically Claimed, Effectively Empty

What Range This Port Belongs To

Port 2384 falls in the registered ports range (1024–49151), the middle tier of the port numbering system.

The three tiers work like this:

• Well-known ports (0–1023): Reserved for foundational Internet services — HTTP on 80, HTTPS on 443, SSH on 22. Requires administrative privileges to bind.
• Registered ports (1024–49151): Assigned by IANA to specific applications upon request. No privilege required to bind, but the assignment creates a soft claim.
• Dynamic/ephemeral ports (49152–65535): Temporary ports assigned by the operating system for outbound connections. No assignments, no expectations.

Port 2384 lives in the registered tier — the part of the port space where developers stake a claim for their application by filing with IANA.

The IANA Registration

IANA lists two entries for port 2384¹:

Both were registered by a private developer with a contact address at sleepdep.net. No RFC exists. No public specification was ever published. The domain is no longer associated with any known service.

The registration is real — it appears in IANA's official registry. The service it represents appears to have never launched publicly, or launched quietly and vanished. What "sd" stood for is lost to time. Sleep deprivation? Service discovery? A project name known only to its author?

This is not unusual. The registered port range contains hundreds of similar entries: names that made sense to someone once, claims staked for projects that never shipped or shipped only internally, ghosts in the numbering system.

Is Anything Actually Running on It?

Almost certainly not — at least, not the service IANA assigned. If you see traffic on port 2384 on your network, it's either:

1. Custom application traffic — A developer chose 2384 for an internal service without knowing or caring about the IANA entry
2. Ephemeral connection traffic — Some operating systems extend their ephemeral range beyond 49152; outbound connections can occasionally use ports in the upper registered range
3. Scanner noise — Automated port scanners probe every port looking for open services

To check what's actually using it on your machine:

Linux / macOS:

# Show what process is listening on port 2384
ss -tlnp | grep 2384
# or
lsof -i :2384

Windows:

netstat -ano | findstr :2384

If nothing comes back, nothing is listening. That's the expected result.

Why Unclaimed Ports Still Matter

The registered port range isn't just an address book — it's a coordination mechanism. When two developers independently choose port 2384 for their applications, they collide. One of them finds the port already in use and has to reconfigure.

IANA registration exists to prevent that collision. Even a dormant registration like port 2384's serves a purpose: it signals "someone filed a claim here." Any developer building a new service should check the registry before choosing a port, precisely to avoid picking one that's already soft-claimed.

The ghost entries aren't noise. They're load-bearing ghosts.