Port 1618: Skytelnet — The ghost in the registry

Port 1618 lives in two worlds at once. The IANA registry says this port belongs to "skytelnet," registered to Byron Jones. But if you search for skytelnet documentation, protocol specifications, or active deployments, you'll find almost nothing. The name exists in the official record and nowhere else.

Meanwhile, in the real world, port 1618 carries Oracle Forms and Reports traffic.¹ Oracle's enterprise application development platform uses this port for communication between clients and servers—a completely different service from whatever skytelnet was meant to be.

This is what happens when the Internet's phone book and reality drift apart.

What the Registry Says

According to IANA's official Service Name and Transport Protocol Port Number Registry, port 1618 is assigned to "skytelnet" for both TCP and UDP.² The registration exists. The assignee exists. But the protocol itself has vanished from common knowledge and active use.

No RFCs document skytelnet. No modern software advertises support for it. The name survives only as an entry in a database that almost no one checks.

What Actually Uses Port 1618

Oracle Forms and Reports services use port 1618 for client-server communication in enterprise deployments.³ When a Forms client connects to a Forms Server runtime process, that connection often runs through 1618. It's not the only port Oracle uses—Forms can use port ranges for runtime communication—but 1618 appears frequently in Oracle documentation and real-world configurations.

This isn't an official IANA assignment to Oracle. This is Oracle using an available registered port that happened to work, and that use becoming widespread enough that port scanners and documentation now associate 1618 with Oracle more than with skytelnet.

The Registered Port Range

Port 1618 falls in the registered port range (1024-49151). These ports are assigned by IANA through a review process defined in RFC 6335.⁴ Companies and developers can request a port for their protocol or service, and if approved, that port gets listed in the official registry.

But registration doesn't mean enforcement. There's no Internet police checking whether the traffic on 1618 actually matches the skytelnet protocol specification (which may not even exist in accessible form anymore). If software uses 1618 for something else, it just does. The registry is a best-effort coordination system, not a mandate.

This is why you find ports where the official name and the actual use don't match. Skytelnet got the reservation. Oracle got the traffic.

Checking What's Listening

To see what's actually using port 1618 on a system:

On Linux or macOS:

sudo lsof -i :1618
sudo netstat -tulpn | grep 1618

On Windows:

netstat -ano | findstr :1618

You'll likely find either nothing (the port is unused) or Oracle Forms/Reports processes. You probably won't find anything calling itself skytelnet.

Why This Matters

The ghost registrations matter because they show how the Internet actually works versus how we document it. The official registry is a map, but the territory changes. Protocols disappear. New services claim old ports. The IANA database becomes a historical record of what was intended, not always what is.

Port 1618 reminds us that assignments are coordination, not law. Skytelnet was here first, at least on paper. But Oracle's the one still showing up.