The Registration That Time Forgot
Port 1359 is officially registered with IANA for a service called "ftsrv" on both TCP and UDP.1 The name suggests "File Transfer Server" but that's speculation—there's no RFC defining it, no documentation explaining how it works, and no evidence of widespread use.
This is what happens when a port gets registered but the protocol never catches on. The number sits in the registry, reserved but essentially unused, while the Internet moves on to other solutions.
What Range This Port Belongs To
Port 1359 falls in the registered ports range (1024-49151). These are ports that organizations can request from IANA for specific services. Unlike well-known ports (0-1023) which require root privileges, registered ports can be used by regular user applications.
IANA maintains the registry to prevent conflicts—if two different services both claimed port 1359, chaos would follow. But registration doesn't guarantee adoption. FTSRV got its number, but apparently nobody used it.
What Actually Runs Here
In practice? Probably nothing. Port 1359 doesn't appear in common network scans, isn't listed in security advisories for active exploits, and isn't documented in any major protocol implementations.
If you find something listening on port 1359, it's likely:
- A custom application that chose this port because it was available
- Malware hiding in an obscure port number
- A legacy system running software from the 1990s
How to Check What's Listening
On Linux or macOS:
On Windows:
If you find something running, the process name will tell you more than the port number ever could.
Why Unassigned Ports Matter
Even though FTSRV appears dead, the port isn't technically unassigned. And that distinction matters.
When developers need a port for a new protocol, they check the registry. If 1359 shows up as taken, they move on. The registration prevents someone else from claiming "ftsrv" and creating confusion decades later.
Unassigned ports (the ones IANA hasn't allocated to anyone) live in the registered range waiting for someone to request them. Each one is a potential home for a future protocol—the next SSH, the next HTTPS, the next thing that millions of devices will depend on.
Port 1359 had its chance. It got registered, got its name in the official record, and then... nothing. The Internet is full of these ghosts—protocols that were proposed, registered, and forgotten.
The Honest Truth
If you're here because something is using port 1359 on your network, the port number won't tell you what it is. The FTSRV registration is too obscure to mean anything useful.
Check the process. Google the application name. Port 1359 is just a number. What matters is what's actually listening.
A fost utilă această pagină?