Port 933: Unassigned — The ghost of Apple's NetInfo

Port 933 sits in the well-known range (0-1023), managed by the Internet Assigned Numbers Authority (IANA). According to the official registry, both 933/TCP and 933/UDP are unassigned—available for any organization to claim.¹

But if you scan an old Mac and find port 933 listening, you haven't discovered a security breach. You've found archaeological evidence.

What Lived Here

Port 933 was used by NetInfo, Apple's directory service that managed user accounts, groups, email configurations, printers, and network resources on Mac OS X systems from 2000 to 2005.²³

NetInfo was inherited from NeXTSTEP when Apple acquired NeXT in 1997. It was a hierarchical distributed database—elegant in theory, frustrating in practice. Network administrators found it confusing. Users found it opaque. And when Mac OS X Tiger (10.5) shipped in 2005, NetInfo was gone entirely, replaced by Open Directory.⁴

The service disappeared. The port remained unassigned.

The Well-Known Range

Port 933 sits in the well-known ports range (0-1023), also called the system ports. These are the prime real estate of the port number system—historically reserved for services so fundamental that they need universal recognition.⁵

IANA controls this range with strict policies. You can't just grab a well-known port for your application. You need to demonstrate that your protocol serves a broad Internet-wide purpose and has gone through the IETF standardization process.⁶

Port 933 is unassigned, which means:

• It's available for official assignment if someone applies through IANA
• It shouldn't be running anything on a modern system
• If you find it listening, something unusual is happening

What You Might Find

On ancient Mac systems (pre-2005), you might still encounter NetInfo traffic on this port. More likely, you'll find:

• Nothing — The port is closed, as it should be
• Malware — Attackers sometimes squat on unassigned well-known ports, betting that administrators won't notice unusual traffic in the "trusted" range
• Custom software — Someone chose 933 for internal tooling without checking the registry

How to Check What's Listening

On macOS or Linux:

sudo lsof -i :933

On Windows:

netstat -ano | findstr :933

If something is listening and you don't recognize it, investigate. Well-known ports shouldn't be occupied by unidentified processes.

Why Unassigned Ports Matter

The Internet has 65,535 ports per protocol (TCP and UDP). Only 1,024 of them are in the well-known range. Yet hundreds of these ports—like 933—sit empty.⁷

They're not wasted. They're waiting. The networking landscape changes. New protocols emerge. Old services die. And occasionally, someone comes along with a service important enough to deserve a well-known port number.

Port 933 is a reminder that the Internet forgets nothing. NetInfo vanished from every production system decades ago, but its port number persists—empty, available, and carrying the faint archaeological trace of Apple's abandoned directory service.

Somewhere in the well-known range, there's a port number with your protocol's name on it. Just make sure what you're building deserves to live in the same neighborhood as SSH, HTTP, and DNS.