Port 2072: mSync — Reserved for a Protocol Still in Draft

What Port 2072 Is

Port 2072 is registered to mSync (service name: msync), a protocol developed by GlobeCast for synchronizing multicast video delivery over satellite networks with conventional HTTP adaptive streaming. Both TCP and UDP are listed.

In practice, you're unlikely to encounter mSync traffic on this port. The protocol never became a finalized standard, and there are no widely deployed implementations.

The Registered Range

Port 2072 falls in the registered port range (1024-49151). This range sits between the well-known ports (0-1023), which require root privileges and host the Internet's foundational protocols, and the ephemeral ports (49152-65535), which operating systems assign temporarily to outbound connections.

Registered ports don't require special privileges to use, and IANA maintains their assignments to prevent conflicts. Any organization can apply to register a port for a specific service, provided it's not already taken.

The Story Behind the Assignment

GlobeCast is a satellite broadcast infrastructure company — the kind of business that distributes television channels to broadcasters and streaming platforms worldwide. They operate satellite uplinks, fiber networks, and IP delivery systems.

At some point, GlobeCast developed mSync to solve a specific problem: when you deliver video over IP multicast (particularly via satellite), receivers need to stay synchronized with the rest of the streaming ecosystem, which uses HTTP adaptive streaming (HLS, DASH, CMAF). mSync was designed to bridge that gap — a transport protocol that carried media segments and manifests over multicast while staying in sync with unicast HTTP delivery.

They submitted it to the IETF as an Internet Draft. The draft reached version 19.¹ It never became an RFC.

IANA registered the port anyway. That's how this works: a company secures a port assignment based on their intent to use it, regardless of whether the underlying protocol ever ships.

What's Actually Listening Here

Almost certainly nothing mSync-related. If you see traffic on port 2072, it's most likely:

• Custom application traffic from software that chose this port informally
• A misconfigured or non-standard service
• Malware or scanning tools using obscure ports to avoid detection

To check what's using port 2072 on your system:

# macOS / Linux
sudo lsof -i :2072
sudo ss -tlnp sport = :2072   # Linux
netstat -an | grep 2072

# Windows
netstat -ano | findstr :2072

Why Unassigned (and Lapsed) Ports Matter

The port registry is a shared namespace. Without it, two applications wanting port 2072 would have no mechanism for avoiding each other. The registration system is mostly honor-based — IANA can't technically enforce exclusivity — but it provides a reference point that developers actually check.

Ports like 2072 represent a common state: registered with clear intent, never fully deployed. They're not wasted space. They hold open the possibility of a protocol that might still ship — and in the meantime, they document someone's attempt to solve a real problem.