Port 960 — Unassigned

Status: Unassigned
Range: Well-known ports (0-1023)
Protocol: TCP/UDP
IANA Assignment: None

What This Port Is

Port 960 is unassigned. It has no official service, no RFC defining its purpose, no protocol waiting on the other side.

It sits in the well-known ports range—ports 0 through 1023—which IANA reserves for system services and widely-used protocols. These are the ports that required special privileges to bind to on Unix systems, the ones that were supposed to be important enough to merit protection.

But port 960 never got claimed.

According to IANA's Service Name and Transport Protocol Port Number Registry, ports 954 through 988 remain unassigned.¹ That's a 35-port gap in a range where every number was supposed to count.

Why Unassigned Ports Exist

The well-known ports range was defined in the early days of the Internet, when 1,024 ports seemed like plenty of space for every important service humanity would ever create.

Some ports got assigned immediately:

• Port 22 for SSH
• Port 80 for HTTP
• Port 443 for HTTPS

Others were reserved for protocols that seemed essential at the time but faded into obscurity. And some—like port 960—were simply held back, reserved but never assigned, waiting for a service important enough to claim them.

The gap exists because IANA is conservative. They don't assign well-known ports casually. The process requires IETF review or IESG approval,² and the service requesting the port needs to demonstrate that it's genuinely important enough to occupy this protected space.

Port 960 never met that bar. Not because it's unusable—it works fine. Just because no one ever needed it badly enough.

What Range This Port Belongs To

Port 960 is part of the well-known ports (also called system ports)—the range from 0 to 1023.

This range has special meaning:

• Requires elevated privileges — On Unix-like systems, only root can bind to these ports
• Reserved by IANA — Assignment requires formal approval
• Expected to be stable — Services here aren't supposed to change

Above this range sit:

• Registered ports (1024-49151) — Assigned by IANA but anyone can use them
• Dynamic/ephemeral ports (49152-65535) — Never assigned, used for temporary connections

Being in the well-known range means port 960 was considered potentially important. It just never became important.

Could Something Be Listening Here?

Yes. Unassigned doesn't mean unused.

Any application can bind to port 960 if it wants to. There's no official service claiming it, but that doesn't stop:

• Custom internal applications
• Malware looking for an uncommon port
• Misconfigured services that picked a random number

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

Linux/macOS:

sudo lsof -i :960
# or
sudo netstat -tuln | grep :960

Windows:

netstat -ano | findstr :960

If you see something listening here, it's not an official service. It's something custom—possibly legitimate, possibly not.

Why This Port Matters

Port 960 matters because it doesn't matter.

It's a reminder that the Internet's address space isn't infinite, that the well-known ports range is a finite resource, and that not every reserved number finds a purpose.

It's also a reminder that IANA's conservatism has been wise. If they'd assigned ports freely in the 1980s, we'd have run out of well-known ports decades ago. The gaps—the unassigned ports like 960—are buffer space. Room for future protocols we haven't imagined yet.

Maybe someday port 960 will get claimed. Someone will design a protocol important enough to need a well-known port, and 960 will finally have a purpose.

Until then, it waits.