Port 1559: web2host — The ghost in the registry

Port 1559 is officially registered in the IANA port registry for a service called "web2host." The registration lists Stephen Johnson as the assignee and indicates the port works with both TCP and UDP.¹

That's where the trail goes cold.

A Registration Without a Protocol

Search for information about the web2host protocol and you'll find almost nothing. No RFC. No documentation. No evidence that the service was ever widely deployed or used. The name suggests some kind of web-to-host communication service from the 1990s, but what it actually did remains a mystery.

Port 1559 sits in the registered ports range (1024-49151)—the section of the port system where IANA assigns numbers to specific services through formal processes. Someone went through the effort of registering this port. Someone had a vision for what web2host would become.

And then... nothing.

The Registered Ports Range

Port 1559 belongs to the registered ports (1024-49151), also called User Ports. Unlike well-known ports (0-1023) which require IETF Standards Action to assign, registered ports use less stringent processes: IETF Review, IESG Approval, or Expert Review.²

This makes the registered range more accessible—you don't need to write an RFC or gain consensus from the entire Internet engineering community. You just need a legitimate service and a reason to request a port.

The trade-off is that registered ports often go unused. Someone registers a port for a service they're developing, but the service never gains traction. The registration remains in the IANA database indefinitely, a placeholder for a protocol that never materialized.

Why Unused Ports Matter

Port 1559 isn't truly "empty." While the original web2host service appears defunct, the port remains officially assigned. This creates an interesting situation:

It's registered but available. Technically, IANA has allocated port 1559 to web2host. In practice, since the service doesn't exist, the port is effectively unused. Other services could theoretically use it informally, though they'd risk conflicts if web2host ever resurfaced.

It shows the registry's history. Every registered port tells a story about what someone thought the Internet needed. Some of those stories have happy endings—protocols that became essential infrastructure. Others, like port 1559, are stories of ideas that didn't take hold.

It demonstrates the permanence of allocation. Once a port is registered, it generally stays registered. The IANA doesn't reclaim unused ports aggressively. This preserves the integrity of the registry but also means ghost ports accumulate over time.

How to Check What's Using Port 1559

Even though the official web2host service appears defunct, any application could theoretically listen on port 1559. To check what's using this port on your system:

On Linux/macOS:

# See what's listening on port 1559
sudo lsof -i :1559
netstat -tulpn | grep :1559

On Windows:

# Find processes using port 1559
netstat -ano | findstr :1559

If you find something listening on port 1559, it's almost certainly not the original web2host service. It's more likely a custom application, a game server, or some other software that chose this port because it's officially registered but practically unused.

The Archaeology of Ports

Port 1559 is a reminder that the IANA port registry isn't just a technical directory—it's an archaeological record. Every entry represents someone's attempt to build something on the Internet. Some of those attempts succeeded spectacularly. Others vanished, leaving only a number and a cryptic name in a database.

Web2host is gone. The port remains. And every time a packet arrives at port 1559, it knocks on the door of a service that isn't there—and hasn't been for decades.