Port 1693: rrirtr — A Name Without a Protocol

What Port 1693 Is

Port 1693 sits in the registered ports range (1024 to 49151). IANA has assigned it a service name: rrirtr, listed for both TCP and UDP. That's where the official record ends.

No RFC defines the protocol. No documentation explains what "rrirtr" stands for. No known software ships with port 1693 as a default. The registration exists in the IANA registry, but the protocol behind it — if one ever existed — never made it into the public record.¹

The Registered Ports Range

Ports 1024 through 49151 are registered ports. The system works like this: an organization or developer requests that IANA associate a port number with their service, so that different applications don't accidentally collide on the same port. Registration is an act of coordination, not enforcement.

The result is a registry of thousands of entries — some representing thriving protocols with RFCs and global deployments, others representing intentions that never became implementations. Port 1693 appears to be the latter.

What You Might Find on Port 1693

If you see traffic on port 1693 on your network, it isn't coming from a standard application using the registered "rrirtr" service. It's more likely:

• Custom or proprietary software that chose this port because it appeared uncontested
• Malware scanning for or using obscure ports to avoid detection (port 1693 has no standard firewall rules to block it)
• A misconfigured service that should be running on a different port

Unassigned-in-practice ports like this are sometimes attractive to software that wants to avoid the well-watched ranges.

How to Check What's Listening

# Linux/macOS: show what process is bound to port 1693
sudo ss -tlnp | grep 1693
sudo lsof -i :1693

# Windows: show listening ports with process IDs
netstat -ano | findstr :1693

If something is listening on port 1693 and you didn't put it there, investigate. The name "rrirtr" won't help you — but the process ID will.

Why This Port Exists at All

The IANA registry is a coordination mechanism, not a guarantee of vitality. Over decades, thousands of port assignments have accumulated — some from organizations that dissolved, some from protocols that were designed but never deployed, some from registration requests where the applicant simply never published their work.

Port 1693 is honest evidence of this: a port number that went through the official process of being claimed, and then went quiet. The Internet kept running. The port kept waiting.

The registry matters anyway. Even a dormant registration means that no one else will accidentally deploy a conflicting service on 1693 — the space is held, even if nothing fills it.