Port 972: Unassigned — A reserved space in the well-known range

Port 972 is unassigned. It has no official service, no RFC defining its purpose, no protocol claiming it. According to IANA, ports 954-988—a block of 35 consecutive ports—remain unclaimed in the well-known range.¹

This is more interesting than it sounds.

What It Means to Be Unassigned

The well-known port range (0-1023) is special. These ports require IETF review or IESG approval to claim.² You can't just decide your application should use port 972. The protocol has to be important enough, standardized enough, widely adopted enough to justify permanent residence in this restricted space.

Port 972 is available for both TCP and UDP. It's ready. It's just waiting for something worthy.

Why Unassigned Ports Matter

The Internet could have assigned all 1024 well-known ports decades ago. Instead, only about 300 are officially claimed. The rest—including port 972—remain deliberately empty.

This isn't an oversight. It's restraint.

Every protocol that gets a well-known port becomes part of the permanent infrastructure. SSH gets port 22. HTTPS gets port 443. These numbers don't change. They can't change. Millions of devices, thousands of RFCs, decades of documentation all reference these exact numbers.

Port 972 sits empty because we haven't needed it yet. And that's fine. Better to leave it available than to assign it to something that won't last.

The Well-Known Range

Ports 0-1023 were the original port space—designed when the Internet was young and every protocol felt essential. Today, we're more careful. The registered port range (1024-49151) exists for applications that need a number but don't require the permanence of the well-known range.

Port 972 lives in well-known territory. If you see traffic on this port, something unofficial is happening. Maybe a custom application. Maybe a test. Maybe someone who didn't know better. But nothing standard.

How to Check What's Listening

Even though port 972 has no official service, something could still be using it on your system. Here's how to check:

On Linux or macOS:

# See what's listening on port 972
sudo lsof -i :972

# Or using netstat
sudo netstat -tuln | grep :972

On Windows:

# Check if port 972 is in use
netstat -ano | findstr :972

If you find something listening on port 972, it's worth investigating. Legitimate services should be using assigned ports. Unassigned ports sometimes attract malware or unauthorized services precisely because nobody expects traffic there.

The Block: 954-988

Port 972 isn't alone. It's part of a 35-port block that IANA has left unassigned. This suggests the block might be reserved for future use—perhaps for a protocol suite that needs multiple consecutive ports, or just maintained as available space for whatever comes next.

The Internet has been running for decades on fewer than 300 well-known ports. We still have over 700 waiting. Port 972 is one of them.

What This Port Carries

Right now? Nothing. No RFC. No standard. No established service.

But that's the honest answer. And sometimes the honest answer is the most important one.