Port 1728: Telindus — A port that outlived its company

What This Port Is

Port 1728 is registered in the IANA Service Name and Transport Protocol Port Number Registry under the name telindus, assigned for both TCP and UDP. It has no well-known protocol running on it today, no active open-source implementation, and no meaningful presence in modern network traffic.

It is, in the most honest sense, a fossil.

The Company Behind the Name

Telindus was a Belgian network infrastructure and ICT company founded in 1969 by John Cordier in Heverlee, near Leuven. It grew across Europe through acquisitions, built carrier-grade IP networks, designed DSL access infrastructure, and managed WAN connectivity for enterprises throughout the Benelux region.

In 2006, Belgacom — Belgium's dominant telecommunications operator — acquired Telindus. On January 4, 2010, Belgacom formally dissolved Telindus as a legal entity and absorbed its operations entirely. The Telindus brand continued to be used in Luxembourg and the Netherlands under what eventually became the Proximus Group, but the original company was gone.¹

The IANA registry still says "telindus" next to port 1728. The port registration outlived the company.

What Range This Port Belongs To

Port 1728 falls in the registered ports range: 1024 through 49151. These ports are distinct from:

• Well-known ports (0-1023): Reserved for core Internet protocols — HTTP, HTTPS, SSH, DNS. Require elevated privileges to bind on most operating systems.
• Registered ports (1024-49151): Assigned by IANA to specific applications upon request. No elevated privileges required, but IANA tracks the assignment to prevent collision.
• Dynamic/ephemeral ports (49152-65535): Used temporarily by operating systems for outgoing connections. Not assigned to specific services.

Registered ports carry IANA's blessing but not necessarily IANA's enforcement. Any application can use port 1728. The registration is a coordination mechanism, not a lock.

No Commonly Observed Unofficial Uses

Port 1728 has no widely documented unofficial uses. Port scanning databases note it only in passing, and there are no known active services, peer-to-peer applications, or malware families associated with it. If you see traffic on port 1728 in your environment, it almost certainly belongs to something specific to your applications or infrastructure — not a standard protocol.

How to Check What's Listening

If port 1728 is open on a system you manage, these commands will tell you what's using it:

On Linux/macOS:

# Show process listening on port 1728
ss -tlnp sport = :1728

# Or with lsof
lsof -i :1728

On Windows:

netstat -ano | findstr :1728

Then match the PID to a process name in Task Manager or with:

tasklist | findstr <PID>

Why Unassigned and Dormant Ports Matter

The registered port range has 48,128 slots. Most are occupied by similarly quiet registrations — products discontinued, companies acquired, protocols never widely adopted. They form a kind of archaeological layer beneath the Internet's active infrastructure.

This matters for security. An open port on a system should have an explanation. "Port 1728 is registered to a company that dissolved in 2010" is not an explanation for why it's open on your server. If something is listening there, find out what it is.

The port system works because applications coordinate around assignments. When a registration goes dark, the port doesn't become dangerous — it just becomes unclaimed territory. Available for whatever shows up next.