Port 1806: Musiconline — A Ghost in the Registry

What Port 1806 Is

Port 1806 is assigned to a service called Musiconline in the IANA Service Name and Transport Protocol Port Number Registry.¹ The assignment covers both TCP and UDP. The registrant is listed as Craig Weeks.

That is nearly everything known about it.

There is no RFC. No documentation. No archived software. No forum posts about configuring it. Musiconline appears to be a product or service from the late 1990s or early 2000s — the first era of Internet music, when streaming was young and dozens of services competed to define what online music would look like. Most of them lost. Most of them vanished. Most left their port numbers behind like luggage abandoned at a train station.

What Range This Port Belongs To

Port 1806 sits in the registered ports range: 1024 to 49151.

The registered range is the middle tier of the port system:

• Well-known ports (0–1023): Reserved for core Internet protocols. HTTP, HTTPS, SSH, DNS, SMTP. You need elevated privileges to bind these on most systems.
• Registered ports (1024–49151): Assigned by IANA to specific applications upon request. No special privileges required to use them. This is where most application-layer protocols live.
• Dynamic/ephemeral ports (49152–65535): Not assigned to anything. Used temporarily by operating systems for outbound connections.

Registering a port in the 1024–49151 range requires submitting a request to IANA. It does not require the service to actually work, remain active, or ever ship to users. The registry is a record of intent — not of deployment.

Ghost Registrations

The IANA registry has thousands of entries like Musiconline: a name, a port number, a contact, and nothing else. Many were registered during the dot-com era when companies anticipated needing dedicated port assignments for services that never launched — or launched and disappeared within a few years.

These ghost registrations matter for one practical reason: if you see traffic on port 1806, it is probably not Musiconline. It is almost certainly something else — a custom application, a game server, malware, or a service that chose this port because it appeared uncontested.

An "assigned" port with no active software is, functionally, an unassigned port. Anyone can use it. Almost no one will recognize it.

Checking What's on Port 1806

If port 1806 shows up in your network traffic or on a system you administer:

See what's listening locally:

# Linux/macOS
ss -tlnp | grep 1806
lsof -i :1806

# Windows
netstat -ano | findstr :1806

Check from outside:

nmap -sV -p 1806 <target-ip>

The -sV flag attempts to identify the service by probing the port — useful when you have no idea what's running.

If something is listening on 1806, treat it like any unknown port: find out what process owns it, verify it's supposed to be there, and confirm it's not exposed to the Internet unless intentional.

Why This Matters

The port registry is not a guarantee of occupancy. It is more like a phone book — a record of who claimed what, not of who is still there.

Port 1806 is a small example of a larger truth about the Internet's nervous system: the official record and operational reality diverge constantly. Ports get claimed and abandoned. Services migrate to new ports. Software ships with hardcoded port numbers that never got registered. The actual traffic on any given port is determined by what software runs in the world, not by what IANA wrote down years ago.

If you are designing a service and need a port, check not just whether a port is unassigned, but whether it is actually unused — those are different questions.