Port 2466: lbf — Registered, Forgotten

What Port 2466 Is

Port 2466 is registered with IANA under the service name lbf — Load Balance Forwarding — for both TCP and UDP. The registrant is Kazuhiro Koide at PFU Limited (pfu.co.jp), a Fujitsu subsidiary better known for making the Happy Hacking Keyboard and ScanSnap document scanners.¹

There is no RFC. No protocol specification. No documentation of what "Load Balance Forwarding" meant to whoever filed the registration. If this port was ever part of a real product or internal system, that history didn't make it into any public record.

In practice, port 2466 behaves like an unassigned port: nothing listens on it by default, nothing is standardized to use it, and no widely deployed software targets it.

The Registered Port Range

Port 2466 sits in the registered ports range (1024–49151). This range is different from the well-known ports below 1024 in one important way: you don't need root or administrator privileges to open a registered port. Any user-level process can bind to it.

IANA maintains registrations in this range to prevent collision — the idea being that if your load balancer and my database both want port 2466, having a registry means one of us registers and the other finds somewhere else. In practice, the registry is full of entries like this one: names without specifications, contacts at organizations that may have restructured or forgotten the filing entirely.

Registration is not the same as deployment. This port is registered. It is not, in any meaningful sense, used.

What Might Actually Be on Port 2466

If you see traffic on port 2466, it isn't the ghost of PFU's load balancer. More likely explanations:

• Application-assigned: Some software chose this port arbitrarily for internal communication — it's uncontested, which makes it convenient
• Dynamic assignment: Operating systems sometimes use registered ports as ephemeral ports for outbound connections, depending on configuration
• Custom service: An internal tool or proprietary system using the port because nothing else does

How to Check What's Listening

macOS/Linux:

lsof -i :2466

or

ss -tlnp | grep 2466

Windows:

netstat -ano | findstr :2466

Then cross-reference the PID with Task Manager or ps aux to identify the process.

If nothing is listening, that's the most common result. The port exists in the registry, but not on your machine.

Why This Matters

The port registry has tens of thousands of entries like port 2466: registered years ago, never standardized, contact information pointing at someone who may have left the company before the filing was complete. The registry was designed to prevent chaos, but it can only do that when registrations are backed by actual specifications.

The real lesson from ports like 2466: a port number means nothing without a protocol behind it. The number reserves space. The protocol — the handshake, the message format, the rules — is what actually carries information. Port 2466 has the number. The protocol never arrived.