Port 2714: Raven Trinity Data Mover — A Registered Ghost

What This Port Is

Port 2714 sits in the registered ports range (1024–49151) and carries an official IANA assignment: Raven Trinity Data Mover (raventdm), supporting both TCP and UDP.

The companion port is 2713, assigned to Raven Trinity Broker Service (raventbs). The naming suggests a two-component architecture: a broker that managed or coordinated transfer jobs, and a data mover that actually executed them. The assignee on record is Daniel Sörlöv, a Swedish technologist specializing in security and infrastructure.¹

Beyond that, the trail goes cold. No public documentation, no source code repository, no user forum post survives. Raven Trinity appears to be one of the IANA registry's many ghost registrations — formally assigned, functionally defunct.

What the Registered Port Range Means

IANA divides the 65,535 ports into three bands:

The registered range was designed for legitimate applications to claim a home. Unlike well-known ports (HTTP, SSH, DNS), these aren't universally recognized by your OS — they only mean something if you're running the specific software that uses them. If Raven Trinity isn't installed, port 2714 is just empty space.

The registry is also a historical artifact. Assignments accumulate over decades. Software gets abandoned. Companies fold. Contact information goes stale. The IANA registry doesn't purge defunct entries — so ports like 2714 remain officially spoken for, even when no one's home.

What to Do If You See Activity on Port 2714

If something is listening on port 2714 on your system, it almost certainly isn't Raven Trinity Data Mover. More likely candidates: custom application, security scanner, malware, or a developer who picked this port arbitrarily because it looked unoccupied.

On Linux/macOS:

# Show what process is listening on port 2714
sudo lsof -i :2714

# Or with ss (faster on modern Linux)
sudo ss -tlnp sport = :2714

On Windows:

netstat -ano | findstr :2714

The PID in the output maps to a process. On Windows, cross-reference with Task Manager. On Linux, lsof gives you the process name directly.

Why Ghost Registrations Exist

The registered port range was created with good intentions: give legitimate software a stable address. In practice, the system has no enforcement. Anyone can request a port. No one checks whether the software is still in use ten years later.

This creates an interesting problem for developers choosing ports for new applications. The "registered" label doesn't guarantee the port is actually safe to use — another application might have claimed it first, even if that other application is Raven Trinity and hasn't been installed on any machine since 2006.

The pragmatic answer: check what's already on a port before committing to it, regardless of what the registry says.