Port 1384: Objective Solutions License Manager — A Forgotten Gatekeeper

Port 1384 sits in IANA's official registry with a service name that almost nobody recognizes anymore: "Objective Solutions License Manager."¹ It's registered for both TCP and UDP, claimed by someone named Donald Cornwell on behalf of a company that built software licensing infrastructure in the 1990s.

The software is almost certainly gone. The company has no visible trace on the modern web. But the port number remains, reserved forever, waiting for connections that will never come.

What This Port Was For

In the 1990s, software companies faced a problem: how do you make sure people actually paid for your software? One solution was license managers—background services that verified your right to run the application.²

Objective Solutions built one of these systems. Their license manager needed a port number to communicate—to check licenses, verify seats, enforce concurrent usage limits. They registered port 1384 with IANA, and in doing so, claimed a small piece of Internet infrastructure forever.

The protocol is lost. No RFC describes it. No documentation survives in accessible archives. What remains is just the registration—a name in a database, a port number that once meant something specific.

The Registered Port Range

Port 1384 lives in the registered port range (1024-49151)—the middle tier of the port number system.³

These ports require IANA registration but don't need special privileges to use. Any user process can listen on port 1384. Any application can claim it. The registration isn't enforcement—it's coordination. A gentleman's agreement that if Objective Solutions said they were using 1384, everyone else would pick a different number.

Most registered ports serve one of two purposes:

• Active infrastructure — services still in use (like port 3306 for MySQL or 5432 for PostgreSQL)
• Historical claims — reservations that outlived their software

Port 1384 is the second kind. A bookmark nobody visits anymore.

Why Dead Ports Stay Registered

You might wonder: if the software is gone, why not release the port number?

The answer is inertia and caution. IANA doesn't actively audit registrations. Once claimed, port numbers tend to stay claimed. Removing them requires someone to notice, investigate, confirm the service is truly dead, and process the de-registration.

And there's risk. What if the software isn't actually dead? What if some legacy system in a hospital basement or manufacturing plant still runs Objective Solutions License Manager? Reassigning the port could break something critical that nobody remembers exists.

So the ports stay registered. The registry grows but rarely shrinks. Port 1384 keeps its name.

What's Actually Using Port 1384 Today

Probably nothing. Or possibly anything.

Because the original software is gone, port 1384 is effectively available for unofficial use. Some application developer might have picked 1384 arbitrarily for their internal tool. Some malware might use it for command and control. Some network game might have chosen it randomly.

The registration is historical. The actual usage is unknown.

If you see traffic on port 1384, you need to investigate what's actually running:

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

# Or use netstat
sudo netstat -tulpn | grep 1384

# Check both TCP and UDP
sudo ss -tulpn | grep 1384

The answer won't be "Objective Solutions License Manager." It will be whatever decided to use that port, registration be damned.

The Archaeology of Port Numbers

Port 1384 is one of thousands of registered ports that tell stories about software that used to exist. Each registration is a fossil—evidence of infrastructure that someone built, used, and eventually abandoned.

Some registrations are famous (port 80 for HTTP, port 443 for HTTPS). Some are actively maintained by surviving companies. Some are completely forgotten except for an entry in IANA's database and a line in the text file that network engineers occasionally grep through.⁴

Port 1384 falls into the third category. It's not famous. It's not maintained. It's just there—a reminder that everything we build eventually becomes archaeology.

Why This Matters

Unassigned and forgotten ports reveal something true about Internet infrastructure: it accumulates.

Every decision to register a port number is permanent in practice, even if not in theory. Every protocol leaves traces. Every company that once existed leaves shadows in registries and RFCs and mailing list archives.

The Internet is built on layers of decisions made by people and companies that no longer exist, solving problems that no longer matter, using techniques that have been obsolete for decades.

And yet the system keeps working. New protocols route around the old ones. New port numbers get assigned above the forgotten ones. The archaeology doesn't break anything—it just sits there, inert, a history nobody reads.

Port 1384 is part of that history. A service name without a service. A reservation without a purpose. A reminder that most of what we build will eventually become a footnote that nobody looks up.