Port 2136: Unassigned — A Blank Entry in the Registered Range

What This Port Is

Port 2136 has no assigned service. IANA — the Internet Assigned Numbers Authority, which maintains the official registry of port assignments — lists it as unassigned for both TCP and UDP.¹

That's not a gap or an error. Most ports in this range are unassigned. It's the normal state.

The Registered Port Range

Port 2136 falls in the registered port range: 1024–49151.

This middle tier sits between two others:

• Well-known ports (0–1023): Reserved for foundational protocols. HTTP is 80. HTTPS is 443. SSH is 22. These require root/administrator privileges to bind on most operating systems.
• Registered ports (1024–49151): Available for applications to claim through IANA. No privilege required to bind. This is where most server software lives when it needs a stable, predictable port.
• Dynamic/ephemeral ports (49152–65535): Assigned temporarily by the operating system for outbound connections. Never registered, never permanent.

When RFC 6335 was written in 2011, only about 9% of registered ports had official assignments.² Port 2136 is part of the other 91%.

Known Unofficial Uses

No widely observed unofficial uses for port 2136 have been documented in security databases or port registries. It doesn't appear in common malware port lists, game server configurations, or database software defaults.

If you're seeing traffic on port 2136, it's almost certainly something specific to your environment — a custom application, internal tooling, or software that picked an available port.

What's Listening on This Port?

If port 2136 is active on your system, these commands will tell you what's using it:

Linux / macOS:

# Show what process is listening
sudo lsof -i :2136

# Or with ss
ss -tlnp | grep 2136

Windows:

# Show listening ports with process IDs
netstat -ano | findstr :2136

# Then look up the PID
tasklist | findstr <PID>

Why Unassigned Ports Matter

The port number space is a shared namespace. When an application chooses port 2136 for its own use, it's betting that nothing else on that system wants the same number. Usually that bet pays off. Occasionally it doesn't — two applications collide, one fails to start, and someone spends an afternoon debugging a "port already in use" error.

Official registration through IANA is how applications stake a public claim: "this is ours, please don't use it." Port 2136 has no such claim. It's open water.