1. Ports
  2. Port 2127

Port 2127 sits in the registered ports range, which runs from 1024 to 49151. These are ports that organizations and developers can formally claim through IANA — the Internet Assigned Numbers Authority — to signal that their software uses a particular port.

IANA's registry lists port 2127 as assigned to a service called INDEX-PC-WB, for both TCP and UDP. The registrant on file is a James David Fisher. Beyond that, the trail goes cold. No documentation. No RFC. No software anyone has publicly identified. The name "INDEX-PC-WB" suggests something to do with indexing on a PC, possibly a whiteboard application (the "WB"), but that is speculation.

This happens more than you might expect in the registered port range. Someone files a port assignment — the process is not difficult — and the software either never ships, fades away, or was only ever used internally. The IANA entry outlasts the project.

What This Port Range Means

Registered ports (1024–49151) occupy the middle ground of the port number space:

  • Well-known ports (0–1023): Assigned to major protocols. HTTP, HTTPS, SSH, DNS, SMTP. Requires elevated system privileges to bind on most operating systems.
  • Registered ports (1024–49151): For applications and services that want a stable, documented port number. Accessible without root. Can be formally claimed through IANA.
  • Dynamic/ephemeral ports (49152–65535): Assigned temporarily by the operating system for outbound connections. Not registered.

Port 2127 being in the registered range means that, at some point, someone cared enough to file the paperwork. Whatever they built either didn't survive or never saw public use.

Is Anything Actively Using Port 2127?

In practice: possibly your own software. Many applications and game servers choose ports in the registered range without formal IANA registration, and port 2127 has no dominant occupant to conflict with. If you see traffic on port 2127, it is almost certainly something specific to your environment — a local application, a game, a development tool — rather than this historical INDEX-PC-WB registration.

No major malware families are known to use port 2127 as a signature channel.

How to Check What's Listening on Port 2127

If port 2127 is open on your system, you can find out what's using it:

On Linux or macOS:

# See which process is listening on port 2127
ss -tlnp | grep 2127

# Or using lsof
lsof -i :2127

On Windows:

# Show process bound to port 2127
netstat -ano | findstr :2127

# Then look up the PID
tasklist | findstr <PID>

Why Unassigned and Obscure Ports Matter

The port registry is infrastructure. When it works, you know what to expect at each port — SSH at 22, HTTPS at 443. But registered ports with dead-end names like INDEX-PC-WB are a reminder that the registry is only as good as the projects that use it. A name in the list is not a guarantee of a living service.

For network administrators, obscure registered ports are worth monitoring. They are not inherently dangerous, but unexpected traffic on any port — registered or not — warrants investigation. The question is never "is this port official?" It's "do I know what's running here, and did I put it there?"

Was this page helpful?

😔
🤨
😃
Port 2127: INDEX-PC-WB — A Registered Ghost • Connected