Port 354: bh611 — A Ghost in the Registry

Port 354 sits in the well-known port range with an official assignment, but the service it was reserved for has vanished from the Internet's collective memory.

What Lives Here (Officially)

According to IANA's Service Name and Transport Protocol Port Number Registry, port 354 is assigned to a service called bh611.¹ The registration lists John Kelly (johnk@bellhow.com) as the contact, suggesting this was a proprietary service from a company or project called Bellhow.

Both TCP and UDP port 354 carry this assignment. The registration exists. The documentation does not.

The Mystery of bh611

No public documentation explains what bh611 actually was. No RFC describes its protocol. No archived manual describes its purpose. No forum posts from 1990s sysadmins mention configuring it. The service name appears in port lists copied from the IANA registry, then stops.

This is genuinely strange. Most assigned ports—even obscure ones—leave some trace. A mailing list discussion. A vendor manual. A mention in a long-dead product announcement. Port 354 has none of that. Just the assignment itself.

What This Port Range Means

Port 354 falls in the well-known port range (0-1023), also called system ports. This range is controlled by IANA and requires formal approval for assignments.² You can't just grab a port number in this range for your weekend project.

Getting a well-known port assignment meant:

• Your protocol mattered enough to request official registry space
• IANA approved it through formal review procedures
• Someone believed the service would be deployed widely enough to need a standard port

Port 354 passed that bar. Then the service disappeared.

The Bellhow Mystery

The email domain "bellhow.com" offers no additional clues. No archived websites. No product announcements. No trademark records. The company or project vanished as completely as its protocol.

This happens more often than you'd think. The Internet's history is full of ambitious protocols that got assigned ports, shipped briefly, then folded when the company failed or the technology was superseded. But most leave something behind.

Checking What's Actually Listening

If you want to see if anything is using port 354 on your system:

# Check if anything is listening on port 354
sudo lsof -i :354

# Or using netstat
netstat -an | grep 354

# Scan port 354 on a remote host
nmap -p 354 hostname

You'll almost certainly find nothing. This port is assigned but not used.

Why Unassigned Ports Matter

Wait—port 354 is assigned. But functionally, it's unassigned. The service it was reserved for doesn't exist anymore. The port sits empty, registered to a ghost.

This matters because:

The registry preserves history. Even when services die, their port assignments remain. Port 354 is evidence that something called bh611 once existed, even if we've lost every other trace of it.

Assignments are permanent. IANA rarely reclaims assigned ports. Once a number is given out, it stays associated with that service name forever. This prevents conflicts and preserves the historical record.

Empty ports stay reserved. You can't repurpose port 354 for your own bh611 service. The name is taken, even though the original service is gone.

The Akashic Records Have Gaps

The IANA port registry is supposed to be the authoritative directory of the Internet's nervous system. Every port. Every protocol. Every service that matters enough to get a number.

But registries only tell you that something existed, not what it was. Port 354 has an entry. A service name. A contact email at a domain that no longer resolves. That's all.

The real history—what bh611 actually did, what problem it solved, why someone built it—is gone. The registry entry is a tombstone without an epitaph.

Related Ports

Port 354 sits among other well-known ports from the early Internet:

• Port 353: NDSAUTH (Netscape Directory Server authentication)
• Port 355: RSVP Encapsulation (resource reservation protocol)
• Port 356-360: Unassigned officially, though some have unofficial uses

The Truthline

Port 354 is assigned to bh611, registered by John Kelly at bellhow.com, but no public documentation exists about what this service actually was or did. It's a ghost in the registry—preserved in the official directory, but forgotten everywhere else.

The Internet remembers that something was here. It just doesn't remember what.