Port 2980: wimd — The Ghost Registration

What This Port Is Registered For

According to IANA's official registry, port 2980 is assigned to a service called wimd — described simply as "Instant Messaging Service" — on both TCP and UDP.¹

That's where the official record ends. There is no RFC. No documentation. No known software that implements it. No community that uses it. The registration lists a contact name, but the protocol itself never materialized into anything real.

This happens more than you'd think.

The Registered Port Range

Port 2980 sits in the registered ports range (1024–49151). Unlike well-known ports (0–1023), which require root or administrator privileges to bind on most systems, registered ports are accessible by any user-level process.

The registered range exists so that developers can claim a port number for their application through IANA, preventing two separate services from accidentally colliding. In theory, it's an orderly reservation system. In practice, it's also a graveyard of abandoned ambitions — messaging startups that ran out of funding, enterprise protocols that lost the standards war, personal projects that were registered optimistically and then set aside.

Port 2980 is one of those. Someone had a plan for an instant messaging service. They filled out the IANA form. They got their port. The protocol never shipped.

Real-World Traffic on This Port

Because "wimd" never became anything, port 2980 is effectively unclaimed. The traffic you might actually see on it has nothing to do with instant messaging.

The most documented unofficial use: people running web servers on non-standard ports when their ISP blocks port 80. A residential user who wants to host images or serve content from home might redirect traffic to port 2980 as a workaround — not because it's special, but because it's open and unlikely to conflict with anything. It's the same reason any arbitrary high port gets pressed into service.²

If you see traffic on port 2980 in your own environment, it's almost certainly something application-specific or incidental.

What's Actually Listening on This Port

To see if anything on your machine is bound to port 2980:

macOS / Linux:

# Show process listening on port 2980
lsof -i :2980

# Or with ss (Linux):
ss -tlnp sport = :2980

Windows:

netstat -ano | findstr :2980

If nothing comes back, nothing is listening. That's the expected result — this port is functionally unoccupied on almost every system in the world.

Why Ghost Registrations Matter

The IANA port registry isn't a living directory of active services. It's a historical record of reservations, many of which were made during the late 1990s and early 2000s when the Internet was growing fast and everyone was registering ports for protocols they intended to build.

Most of those protocols never arrived. The registrations remain because IANA doesn't revoke them — a port number, once assigned, stays assigned in the official record indefinitely.

This matters practically: if you're choosing a non-standard port for an internal service, checking against the IANA registry tells you whether a number is officially spoken for. Port 2980 technically is. But whether that matters to you depends entirely on your context. No software is going to show up claiming it.