Port 1831: Unassigned — A Registered Port with No Registered Purpose

What Range This Port Belongs To

Port 1831 falls in the registered ports range (1024–49151). These are ports that organizations and developers can formally claim through IANA by submitting an application with a defined protocol and purpose. Well-known services live here: MySQL on 3306, PostgreSQL on 5432, Redis on 6379.

Port 1831 was never claimed. It sits in this range as unclaimed real estate — space reserved for order, never put to use.

What IANA Says

Nothing. Port 1831 appears in the IANA registry as unassigned for both TCP and UDP.¹ No RFC. No service name. No registered owner.

Unofficial Sightings

Some third-party port databases list port 1831 as "myrtle" — a name that appears without explanation, RFC citation, or any traceable origin.² Where this label came from is unclear. It does not correspond to any known application, protocol, or vendor documentation found in public records.

Older security scanning databases have flagged port 1831 as historically associated with malware activity — meaning some trojans have used this port for command-and-control communication.³ This is not unusual: malware frequently migrates to unassigned ports precisely because they lack the scrutiny that port 80 or port 443 receives. A firewall that blocks known services but passes unknowns is a door left ajar.

There is no currently documented active threat specific to this port.

How to Check What's Listening on This Port

If you see traffic on port 1831 and want to know what's generating it:

On Linux/macOS:

# Show the process listening on port 1831
ss -tlnp | grep 1831
# or
lsof -i :1831

On Windows:

netstat -ano | findstr :1831

The last column of netstat output is the process ID (PID). Cross-reference it with Task Manager or:

tasklist | findstr <PID>

If something is listening on port 1831 on your system and you didn't put it there, find out what it is. Unassigned ports are where unexpected things hide.

Why Unassigned Ports Matter

The registered port range contains 48,128 ports. Most are empty. This isn't a problem — it's by design. The system works because assignments are optional, not mandatory. Applications that need a consistent port register one; everything else negotiates dynamically using ephemeral ports (49152–65535).

But the gaps matter for a different reason: they're ambiguous. A packet arriving on port 1831 carries no inherent meaning. Your firewall doesn't know what to do with it. Your IDS has no signature to match against. The emptiness is both the point and the risk.

Registered-but-unassigned ports are the quiet streets of the Internet — mostly fine, occasionally the address of something that doesn't want to be found.