Port 871 sits in the well-known ports range (0-1023), which means it was significant enough to get an early assignment. But if you scan a modern network, you'll rarely find anything listening here. This port carried something that mattered in 1985 and then quietly disappeared.
What Ran on Port 871
Port 871 was assigned to supfilesrv—the server component of SUP (Software Update Protocol). SUP was a file synchronization and distribution system created at Carnegie Mellon University in the mid-1980s.1
The protocol solved a problem that barely exists anymore: how do you keep files synchronized across multiple Unix machines when the Internet has hundreds of hosts instead of billions? Every machine with files worth sharing was expected to run supfilesrv on port 871, waiting for connections from SUP clients that wanted to replicate those files.2
How SUP Worked
When a SUP client connected to port 871, it would request updates for specific file collections. The server would:
- Accept the connection via TCP
- Fork a process to handle the client interaction
- Compare file versions between server and client
- Transfer only the files that had changed
This was file synchronization before rsync, before Git, before most people had modems. The server listened on port 871, and clients across the early Internet connected to pull down updates.3
The History
SUP was documented by S. A. Shafer at CMU's Computer Science Department in 1985.4 The earliest version (supscan) was created on April 4, 1985, with documentation following on May 23, 1985. This was the era when Unix systems at universities were just beginning to network together.
SUP handled both "private" and "system" file collections. A university might use it to distribute software updates across their campus machines. A research lab might use it to keep documentation synchronized. Every SUP server left port 871 open, waiting.
Why It Disappeared
SUP was designed for a specific era of computing—centralized Unix systems at institutions, modest numbers of machines, and trust between hosts. As the Internet grew, better tools emerged:
- rsync (1996) offered more efficient delta encoding
- CVS and later SVN provided version control, not just file copying
- Git (2005) became the dominant distributed version control system
SUP solved file synchronization when synchronization meant "keep the files on these dozen machines identical." Modern tools solve much larger problems. Port 871 became unnecessary.
Current Status
IANA lists ports 863-872 as unassigned in the official registry, despite port 871's historical use by SUP.5 This is honest—the protocol is effectively dead. You won't find supfilesrv running on production systems in 2026.
If you scan port 871 and find it open, you've either discovered:
- A very old Unix system that hasn't been updated in decades
- Someone repurposing an abandoned port for custom software
- A historical curiosity running for nostalgia
How to Check What's Listening
On Linux or macOS:
On Windows:
If something is listening, you can attempt to identify it:
Why Unassigned Ports Matter
Port 871 represents something important about the Internet's evolution: protocols come and go. The well-known ports range (0-1023) contains dozens of these fossils—ports that once carried essential services and now carry nothing.
But the port numbers remain. They're reserved in documentation, remembered in old firewall rules, and occasionally still blocked by security policies that haven't been updated since 1995. The Internet has layers of history embedded in it, and every unassigned port is a reminder that what feels permanent today might be forgotten tomorrow.
SUP was essential for a few years. Then it wasn't. The port remains.
Related Ports
- Port 873 — rsync, the tool that largely replaced SUP for file synchronization
- Port 22 — SSH/SCP, another way to transfer files securely across networks
- Port 9418 — Git protocol, the modern approach to distributed version control
หน้านี้มีประโยชน์หรือไม่?