Port 2649: VPSIPPORT — A Name Without a Story

What Port 2649 Is

Port 2649 sits in the registered ports range (1024–49151). These are ports that organizations and individuals can formally claim through IANA — the Internet Assigned Numbers Authority — to signal intent to use them for a specific service.

IANA's registry shows port 2649 assigned to a service called VPSIPPORT, registered on both TCP and UDP, with a contact named Joon Radley. ¹

That's where the paper trail ends.

The Ghost Assignment

VPSIPPORT has no RFC. No public specification. No known open-source or commercial software that announces it. The name suggests something involving SIP (Session Initiation Protocol, used in VoIP) or possibly "VPS IP" management, but there's no documentation to confirm either reading.

This happens. IANA's registered ports range is first-come, first-served with minimal requirements. Someone fills out a form, claims a port, and sometimes never ships the software — or ships it quietly for internal use only. The port gets a name in a registry and no presence in the world.

How to Check What's Actually Using This Port

If you see traffic on port 2649, it's almost certainly something specific to your environment — an application that chose the port arbitrarily, internal tooling, or malware using an obscure number to avoid scrutiny.

To check what's listening on your system:

Linux / macOS:

# Show what process is listening on port 2649
ss -tlnp | grep 2649
# or
lsof -i :2649

Windows:

netstat -ano | findstr :2649
# Then look up the PID:
tasklist | findstr <PID>

If something's listening and you don't recognize it, that's worth investigating.

Why Unassigned (and Under-Documented) Ports Matter

The registered ports range contains thousands of entries like this one — names without implementations, placeholders that outlasted their projects, or internal tools that never went public. They matter for two reasons:

Security scanning: Port scanners and firewalls use the IANA registry as a baseline for "known" vs. "unknown" traffic. A port with a registered name might get waved through; an unrecognized one might not. Knowing which ports in your range have nominal registrations helps you understand your exposure.

Port selection: If you're building software that needs a port, checking whether a number has any registration — even a ghost one — is worth doing. A clean, truly unassigned port is easier to justify to a security team than one with a mysterious name attached to it.