Port 2424: Unassigned — OrientDB and the Squatters

What Port 2424 Is

Port 2424 sits in the registered port range (1024–49151). IANA maintains this range as a registry where software vendors and protocol designers can formally claim a port for their service. Port 2424 has no such claim on record — IANA lists it as unassigned.

That doesn't mean the port is empty. It means whoever uses it did so without asking.

Who Uses It

OrientDB — Binary Client Protocol

OrientDB, a multi-model database that handles documents, graphs, and key-value data in a single engine, defaults to port 2424 for its binary protocol.¹ When an OrientDB server starts, clients — including OrientDB's own console and native drivers — connect here. The HTTP interface lands on 2480, keeping the two protocols neatly separated.

If OrientDB needs to run multiple instances on the same machine, it steps up through a range: 2424, 2425, 2426, and so on until it finds a free port.² Port 2424 is the first door it tries.

AudioCodes TPNCP — Telecom Control

TPNCP (TrunkPack Network Control Protocol) is AudioCodes' proprietary protocol for controlling their voice-over-packet hardware — the TrunkPack-VoP series of telecom gateways. It runs on both TCP and UDP at port 2424.³ If you're in a telecom environment with AudioCodes gear and you see traffic on 2424, this is almost certainly what you're looking at.

Wireshark has a built-in dissector for TPNCP, though it requires a tpncp.dat file to decode the constantly-evolving protocol definitions.⁴

How to Check What's Listening

# macOS / Linux
sudo lsof -i :2424

# Linux alternative
ss -tlnp | grep 2424

# Windows
netstat -ano | findstr :2424

If OrientDB is running, you'll see its process. If you're in a telecom rack with AudioCodes hardware, you'll see TPNCP traffic. If neither applies and something is listening on this port, it's worth investigating — unassigned ports are occasionally used by malware to avoid detection.

Why Unassigned Ports Matter

The registered port range has 48,128 slots. IANA has formally assigned a fraction of them. The rest exist in a practical gray zone: software vendors pick numbers that seem unlikely to conflict, ship their product, and the de facto assignment sticks for decades.

This is how OrientDB ended up on 2424. It's how many databases, game servers, and internal tools picked their ports. The registry is authoritative on paper; convention governs in practice.

When you're diagnosing a firewall rule, auditing a server, or wondering why something won't connect, the IANA registry is the starting point — but it's not the whole story. Unofficial uses like these are why tools like SpeedGuide and Wireshark maintain their own databases of observed port behavior.