Port 1873: fjmpjps — Registered, Unknown, Effectively Unused

Port 1873 sits in the registered port range (1024–49151). These are ports that organizations and developers can formally claim through IANA, the authority that coordinates the global assignment of port numbers, protocol parameters, and Internet resources.

The IANA registry lists port 1873 as assigned to a service called fjmpjps — for both TCP and UDP. That's where the trail ends. No RFC documents it. No vendor has published documentation for it. No open-source project references it. The name itself is opaque: a string that might be an acronym, a product code, or a typo that survived decades of copy-paste.¹

What "Registered" Actually Means

A registered port assignment does not mean a service is active, maintained, or even real in any meaningful sense. Registration in the IANA database means someone, at some point, submitted a request. The bar for registration is low. The bar for maintaining or documenting what you registered is nonexistent.

The registered port range was designed to give application developers a stable, conflict-free space for their services. It works well for ports like 3306 (MySQL), 5432 (PostgreSQL), or 6379 (Redis) — services with active communities and published protocols. For ports like 1873, the registration is more like a land claim on an empty lot. The sign is there. Nobody lives there.

What Might Actually Use This Port

In practice, port 1873 has no commonly observed unofficial uses. Security databases and port scanners occasionally flag it as generic registered-but-unknown, but there are no widespread reports of malware, tunneling tools, or shadow services operating here.

If you see traffic on port 1873 on your own network, it is almost certainly custom application traffic — an internal service, a developer's test environment, or software that chose this port arbitrarily precisely because nothing else is using it.

How to Check What's Listening

If port 1873 is open on a machine you control, these commands will tell you what's behind it:

On Linux/macOS:

# Show the process listening on port 1873
ss -tlnp | grep 1873

# Alternative using lsof
lsof -i :1873

On Windows:

netstat -ano | findstr :1873

The process name or PID that appears will tell you more than any port database can.

Why Unassigned and Ghost Ports Matter

The port number space is finite: 65,535 ports, shared across every protocol every application might ever need. The registered range exists to prevent collisions — two applications accidentally picking the same port and stepping on each other.

Ghost entries like port 1873 occupy space in that system without contributing to it. They're artifacts of an earlier, less rigorous era of Internet administration. IANA has gradually tightened its standards, but thousands of legacy entries remain.

For network administrators and security teams, ports like 1873 are worth monitoring for a different reason: because they're obscure, attackers occasionally use them for command-and-control traffic or tunneling, betting that nothing is filtering an unrecognized registered port. Obscurity is not security — but it does attract a certain kind of opportunism.