Port 2769: eXcE / Single Point MVS — A name without a presence

Port 2769 has a name — two, actually. IANA lists it as eXcE, and SANS databases reference it as Single Point MVS. Neither service has any meaningful documentation, active user community, or known deployments. In the library of the Internet's ports, this is a shelf with a label and no books.

What Range It Belongs To

Port 2769 sits in the registered ports range (1024–49151). These ports aren't controlled by the operating system the way well-known ports (0–1023) are — any user-level process can bind to them. IANA maintains a registry of assignments in this range, but registration doesn't guarantee a service ever shipped, scaled, or survived.

Think of registered ports as reserved parking spots. Someone filled out the form. Whether they ever parked there is a different question.

The Two Names

eXcE is the name IANA has on file for port 2769 over TCP and UDP. There is no public RFC, no surviving documentation, and no company visibly shipping a product that uses it. The assignment exists in the registry and nowhere else.

Single Point MVS appears in SANS port databases as an alternate name. MVS (Multiple Virtual Storage) is the IBM mainframe operating system that eventually became z/OS. "Single Point" suggests some kind of centralized management interface — but no IBM documentation connects this name to port 2769, and no active tooling references it.

Both names have the character of 1990s or early 2000s software projects that registered a port, then quietly faded.

Neighborhood Context

Port 2769 sits near the 2700–2704 block, which IANA officially assigned to KnowShowGo P2P — a peer-to-peer file sharing protocol from the early 2000s that also left little trace on the modern Internet. The surrounding ports are a neighborhood of forgotten registrations from that era.

What You'll Actually Find Here

In practice, if something is listening on port 2769 on a machine you control, it's almost certainly:

• Custom application software — internal tools sometimes pick ports from the registered range arbitrarily
• Malware — uncommon ports are occasionally used by remote access trojans or C2 infrastructure precisely because they don't attract attention
• A misconfigured service bound to the wrong port

If you didn't put it there intentionally, find out what it is.

How to Check What's Listening

On Linux/macOS:

# Show which process is using port 2769
ss -tlnp | grep 2769
# or
lsof -i :2769

On Windows:

netstat -aon | findstr :2769

Then take the process ID (PID) from the output and look it up:

# Linux/macOS
ps aux | grep <PID>

# Windows (Task Manager, or)
tasklist | findstr <PID>

Why Unassigned-in-Practice Ports Matter

The registered port range contains thousands of entries like this — names attached to services that never gained traction. They matter for a few reasons:

Firewall hygiene. A port you don't use should be closed. Unrecognized traffic on port 2769 is a signal worth investigating, not ignoring.

Port squatting. Malware authors know that security teams focus on well-known ports. Binding to an obscure registered port provides camouflage. An unknown process on port 2769 is more suspicious than a known process on port 80.

The registry as archaeology. The IANA port registry is a partial record of what software projects existed and imagined they'd need. Most of the registered range reflects ambitions that didn't pan out. Port 2769 is one of thousands of these fossils — technically claimed, practically unclaimed.