Port 982: Unassigned — A reserved number with no service

Port 982 belongs to the well-known ports range (0-1023)—the space reserved for fundamental Internet services like HTTP, SSH, and FTP. But unlike its neighbors, port 982 has never been assigned to anything.

What Well-Known Ports Mean

The range from 0 to 1023 is special. These ports are called "well-known" or "system ports," and they're reserved for core network services that need consistent, universal port numbers.¹ When you connect to a web server, you use port 80 or 443 because those numbers are guaranteed to mean HTTP and HTTPS everywhere on the Internet.

Getting a well-known port assignment requires IETF Review or IESG Approval—strict processes that reflect how carefully this range is controlled.² On Unix-like systems, you need root privileges just to bind a service to one of these ports. They're protected because they're supposed to matter.

Port 982's Status

Port 982 is part of the range 954-988, which IANA lists as "Unassigned."³ It's reserved but unclaimed. No protocol owns it. No RFC defines what should run here.

This isn't a registered port (1024-49151) where organizations can request assignments for their services. This is the well-known range. Every number here was supposed to be for something fundamental. Port 982 just never got used.

Why It Exists Anyway

Even unassigned ports serve a purpose. They're placeholders. If a new fundamental protocol needed a well-known port tomorrow, 982 is available. The alternative would be crowding new services into the already-dense registered range or trying to reclaim ports from obsolete protocols—both messier options.

The existence of unassigned well-known ports also reveals something about Internet history. Protocols came and went. Some anticipated services never materialized. Others evolved differently than expected. The gaps are the protocols that weren't.

What Might Be Listening

Just because IANA hasn't assigned port 982 doesn't mean nothing uses it. Developers sometimes choose arbitrary ports for custom services. Malware occasionally squats on unassigned ports precisely because they're not monitored as closely as known services.

To check what's listening on port 982 on your system:

# Linux/macOS
sudo lsof -i :982
sudo netstat -tulpn | grep :982

# Windows
netstat -ano | findstr :982

If something is listening and you didn't deliberately configure it, investigate. Run antivirus scans. Check running processes. Unassigned doesn't mean safe—it just means nobody official claimed the number.

The Unassigned Ports

Port 982 isn't alone. The well-known range has several unassigned blocks. They sit between the ports that shaped the Internet—quiet gaps in a dense neighborhood. Some will eventually get claimed. Others will remain empty, permanent placeholders in a system that was designed with more expansion in mind than it ultimately needed.

This is what infrastructure looks like up close. Not every number has a story. Some are just reserved space, waiting.