Port 2367: Service Control — A Name Without a Service

Port 2367 sits in the registered port range (1024–49151) with a formal IANA assignment: "Service Control," registered to one Humberto Sanchez. No RFC. No widely deployed implementation. No community of users. Just a name in a registry.

This is not unusual. The IANA port registry contains tens of thousands of entries. Some represent protocols that carry the weight of the Internet. Others are reservations made at a moment in time for projects that never launched, never scaled, or simply never needed the registration they filed for.

Port 2367 appears to be the latter.

The Registered Port Range

Ports 1024 through 49151 are registered ports — sometimes called "user ports." Unlike the well-known ports below 1024 (which require root or administrator privileges to bind on most systems), registered ports can be used by any application.

IANA maintains a registry for these ports. Registration signals intent — "we plan to use this port for this service" — but it doesn't guarantee adoption. A port can be registered and still functionally unused by the broader Internet.

Registered ports matter because they prevent collisions. If two applications independently decided to use the same port, every machine running both would have a conflict. The registry is a coordination mechanism. It works best when people consult it before picking a port, and when the services they register actually ship.

What's Actually on Port 2367

In practice, port 2367 has no documented, widespread use. If you see it open on a system, the most likely explanations are:

• A custom application that chose this port for local reasons
• Development tooling using it as an alternative to a nearby port
• Scanning noise — automated systems probing registered ports

Worth noting: port 2368 next door is the default port for Ghost, the open-source publishing platform. Ghost installations often run on 2368 and proxy through a web server on 443. Port 2367 occasionally appears in discussions of Ghost configuration, but as an alternative, not a default.

How to Check What's on This Port

If you see port 2367 active on your system:

macOS / Linux:

# See what process is listening on port 2367
lsof -i :2367

# Or with netstat
netstat -an | grep 2367

Windows:

# Show process using port 2367
netstat -ano | findstr :2367

# Then match the PID
tasklist | findstr <PID>

The process name will tell you whether it's something you installed intentionally.

Why Unassigned-in-Practice Ports Exist

The registry reflects ambition as much as reality. Ports get registered, projects stall, companies pivot, developers move on. The assignment stays. This isn't a failure of the system — it's the cost of running a coordination mechanism for the entire Internet across decades.

The alternative (requiring active re-registration, or reclaiming unused ports) would create its own chaos. A port that's been "unused" for years might quietly power a niche internal tool at one company. IANA errs on the side of stability.

Port 2367 is a placeholder that never filled. The Internet has thousands of them, holding space for things that almost were.