Port 2910: TDAccess — A Named Port That Never Explained Itself

What Range This Port Belongs To

Port 2910 is a registered port — part of the range from 1024 to 49151 managed by the Internet Assigned Numbers Authority (IANA). Unlike well-known ports below 1024 (which require root/administrator privileges and carry foundational protocols like HTTP, SSH, and DNS), registered ports are claimed by applications and services that registered a name with IANA.

Registration doesn't require much. No working implementation, no RFC, no public documentation. Just a name and a contact. Port 2910 proves the point.

The Official Name: TDAccess

IANA lists port 2910 as TDAccess on both TCP and UDP.¹ That's the full extent of the official record. There is no RFC. No description of what TDAccess does, what protocol it speaks, or who runs it. The registration exists. The service, as far as the public record goes, does not.

"TDAccess" may stand for something related to Turbine, the game studio — but this is inference, not documentation. The registry has a name with no story attached.

What Actually Uses Port 2910

In practice, port 2910 shows up in gaming contexts. Turbine, the studio behind Dungeons & Dragons Online and Lord of the Rings Online, uses the UDP port range 2900–2910 for game server traffic.²³ Players who set up port forwarding to reduce lag — or whose firewalls block game traffic — encounter this range directly.

Both games have since transitioned to Standing Stone Games, but the port range persists. If you're running DDO or LOTRO and see traffic on 2910, that's why.

Outside of gaming, no widely documented unofficial use exists. Port 2910 isn't associated with known malware, common development tools, or database systems.

How to Check What's Listening

If port 2910 is open on your machine and you want to know why:

Linux / macOS:

sudo ss -tlnp | grep 2910
# or
sudo lsof -i :2910

Windows:

netstat -ano | findstr :2910

The output will show the process ID. Cross-reference it with your task manager or ps aux to identify the application.

If nothing appears, the port is closed — normal for most machines. If something unexpected is listening, investigate the process before assuming the worst.

Why Unassigned and Obscurely-Named Ports Matter

The registered port range contains thousands of entries like TDAccess: names in a spreadsheet with no supporting documentation, claimed years ago and never explained. This matters for a few reasons.

First, these ports aren't reserved in any meaningful enforcement sense. Any application can bind to port 2910 regardless of the IANA name. The registry is advisory, not policed.

Second, obscure port names create blind spots. When a firewall rule mentions "port 2910," administrators can't look up what it is without digging through multiple databases and often arriving at the same dead end. That ambiguity is a real operational problem.

Third, it illustrates the gap between the IANA registry and actual Internet behavior. The Internet runs on documented protocols and undocumented conventions in roughly equal measure. TDAccess is just an unusually visible example of the latter.