Port 2519: globmsgsvc — Registered, Forgotten

What Port 2519 Is

Port 2519 sits in the registered ports range (1024–49151). IANA lists it as globmsgsvc — presumably "Global Message Service" — assigned to one David Wiltz. That's where the trail ends.

There is no RFC. No technical specification. No description in the IANA registry beyond the name itself. The port was registered, and then apparently nothing happened. Either the service never shipped, was used internally without public documentation, or was simply forgotten.

This is not unusual. The registered ports range contains thousands of assignments, many of them similarly sparse: a name, an assignee, a date, and silence.

What Range This Port Belongs To

Port 2519 falls in the registered ports range: 1024–49151. ¹

These ports differ from well-known ports (0–1023) in one key way: they don't require root or administrator privileges to bind. Any process can listen on port 2519 without elevated permissions. IANA accepts registration requests for these ports, but registration is not mandatory — plenty of legitimate software uses registered-range ports without ever filing paperwork.

The practical consequence: if you see traffic on port 2519, the IANA registry will not tell you what it is. You have to look at what's actually running on your system.

Security Notes

Port 2519 appears on some older trojan and malware port lists, though no specific, named malware is documented as using it. These lists were often compiled by scanning infected machines and noting which ports had unexpected listeners — not by identifying a specific threat.

The honest assessment: there is no known active malware associated with port 2519. If you see unexpected activity here, the cause is almost certainly benign software that chose this port arbitrarily, not a known threat. Investigate anyway.

How to Check What's Listening

Linux / macOS:

sudo ss -tlnp | grep 2519
# or
sudo lsof -i :2519

Windows:

netstat -aon | findstr :2519

The process ID in the output can be matched against Task Manager or tasklist to identify what's actually using the port.

Why Unassigned (and Ghost-Registered) Ports Matter

The port system works because of shared expectations. When a browser connects to port 443, it expects HTTPS. When a mail client reaches port 587, it expects SMTP submission. That shared understanding is what makes the Internet navigable.

Ports like 2519 — registered but undocumented — are edge cases. They occupy a name in the registry without occupying any shared expectation. Software can use them, and frequently does, but without a spec to enforce, what runs on port 2519 on one machine has nothing to do with what runs on port 2519 on another.

That ambiguity is fine. It's part of how the registered range is supposed to work: flexible, claimable, optional. The registry is a coordination mechanism, not a mandate. Port 2519 is just a slot that someone reserved and never fully moved into.