Port 2069 has no officially assigned service. IANA — the Internet Assigned Numbers Authority, the body that manages the global port registry — lists it as unassigned. There is no RFC that defines it, no standard protocol that runs on it, no organization that has claimed it.
What Range It Belongs To
Port 2069 falls in the registered port range: 1024 through 49151.
This range sits between two others with clearer identities. Below it, ports 0 through 1023 are the "well-known" ports — HTTP, HTTPS, SSH, DNS — the ones everyone knows and system privileges protect. Above it, ports 49152 through 65535 are ephemeral ports, the temporary ones your operating system assigns on the fly for outbound connections.
The registered range is the middle ground. IANA accepts applications from software vendors and organizations who want a port number officially associated with their service. Most registered ports do have owners — someone filed the paperwork. Port 2069 never did, or the registration lapsed, or it was simply never applied for.
Known Unofficial Uses
A few things have been observed on port 2069 over the years, none of them standard:
ICUII — A video chat client popular in the late 1990s used port 2069 for client connections. ICUII (pronounced "I See You Too") was an early attempt at Internet video calling before broadband was common. The software is long abandoned, but port databases still list it because they were built in that era and never cleaned up.
Bosch Rexroth ctrlX CORE — This industrial automation platform uses port 2069 for its data layer client communications in some configurations. Industrial control systems often pick ports in the registered range that aren't claimed by anything else — port 2069 was available.
Neither of these represents a standard. If you see traffic on port 2069, it's almost certainly something specific to your environment, not a universal protocol.
How to Check What's Listening
On any Unix-like system (Linux, macOS):
Or with ss:
On Windows:
The process ID in the output can be cross-referenced in Task Manager or with tasklist /fi "pid eq [PID]" to find which application is using the port.
If nothing is listening, the port is closed — packets arriving there will be silently dropped or receive a TCP reset, depending on your firewall configuration.
Why Unassigned Ports Matter
The port system works because of shared expectations. When you connect to port 443, you know you'll find HTTPS. When you connect to port 22, you'll find SSH. That predictability is the point.
Unassigned ports like 2069 are the gaps in that expectation. They exist for good reasons — the address space needs room to grow, and not every application needs a registered port — but they create ambiguity. Malware sometimes hides in unassigned ports precisely because there's no baseline behavior to compare against. A firewall rule blocking "everything unexpected" becomes harder to define when "expected" isn't clearly established.
The practical rule: if something is listening on port 2069 and you didn't put it there, find out what it is before you decide whether to trust it.
Was deze pagina nuttig?