Port 2349 — Unassigned

What Range This Port Belongs To

Port 2349 falls in the registered port range (1024–49151), the middle tier of the port numbering system.¹

The three tiers work like this:

• Well-known ports (0–1023) — Reserved for major protocols. HTTP gets 80, HTTPS gets 443, SSH gets 22. You need root or administrator privileges to bind to these.
• Registered ports (1024–49151) — Available for software vendors and protocol designers to register with IANA. Anyone can submit an application. The range is enormous, and most of it sits empty.
• Dynamic/ephemeral ports (49152–65535) — Your operating system hands these out automatically for outgoing connections. They're temporary by design.

Port 2349 is registered but unclaimed. IANA has no service name, no protocol description, and no point of contact on file for it.²

Unofficial Uses

No widely observed legitimate service uses port 2349. Security databases flag it with a vague "historical malware association"—meaning at some point, something suspicious communicated through this port—but no specific threat has been identified by name.³ This kind of flag is common for unassigned ports: they're attractive to malware precisely because no legitimate software is expected to use them, making anomalous traffic harder to spot.

There's no evidence of any common application, game, or development tool that defaults to this port.

What to Do If You See Traffic Here

If something is listening on port 2349 on your machine and you didn't put it there, find out what it is.

On Linux or macOS:

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

On Windows:

netstat -ano | findstr :2349
tasklist /fi "PID eq <PID_FROM_ABOVE>"

These commands show you which process owns the port. A process you don't recognize listening on an unassigned port is worth investigating.

Why Unassigned Ports Matter

The port registry is mostly holes. Of the 49,152 registered ports, only a fraction have assigned services. The rest are available—first-come, first-served—for anyone who submits a request to IANA, or for anyone who simply starts using one without asking.

This matters for network security because firewalls and intrusion detection systems often work from allowlists: traffic on known ports gets scrutinized, traffic on unknown ports gets blocked or ignored. An unassigned port is a quiet corner. Legitimate software that needs to avoid conflict picks registered-but-unassigned ports. So does software that would prefer not to be noticed.

Port 2349 isn't dangerous by itself. It's just unclaimed territory in a very large registry.