Transport: TCP and UDP Status: IANA-registered (registered ports range, 1024–49151) Assigned service: tapestry
What the Registered Ports Range Means
Port 1922 sits in the registered ports range, sometimes called "user ports." This range runs from 1024 to 49151 and represents a middle ground in the port numbering system.
Well-known ports (0–1023) are reserved for foundational protocols: HTTP on 80, SSH on 22, DNS on 53. You need operating system privileges to bind to them. The registered ports range is different: anyone can apply to IANA to claim a number for their service, and anyone can bind to these ports without special privileges.
IANA assigned port 1922 to a protocol called Tapestry. The assignment is real. What happened next is a story about how research and deployment often diverge.
What Tapestry Was
In 2001, distributed systems researchers were racing to solve a hard problem: how do you find a file in a network of millions of peers, with no central server, efficiently?
Four systems emerged almost simultaneously: CAN, Chord, Pastry, and Tapestry. All four used a structure called a distributed hash table (DHT) — a way of distributing a lookup table across thousands of machines so that any node can find any piece of data in a predictable number of hops.
Tapestry came out of UC Berkeley and HP Labs. Its key insight was location-awareness: routing messages toward the nearest copy of a resource, not just any copy. The 2003 paper published in IEEE Journal on Selected Areas in Communications described a self-repairing overlay network that could route efficiently even as nodes joined and left.1
It was real research solving a real problem. It just never became the protocol that people actually ran.
BitTorrent, which launched in 2001, used a simpler DHT approach that was good enough and easy to implement. Tapestry and its siblings remained largely in academic circles — studied, implemented in research code, built into some experimental systems, and then mostly left there.
The IANA registration for port 1922 is a small fossil of that moment: the early 2000s, when distributed computing researchers believed they were building the foundations of a new Internet.
What You'll Find on This Port Today
Almost certainly nothing related to Tapestry. If you see traffic on port 1922, it's likely one of three things:
- Custom application traffic — developers pick registered ports for their own services all the time, knowing the port is "registered" but unused in practice
- Port scanning or probing — automated scanners sweep all ports
- Malware — some malicious software has used this port for command-and-control communication in the past2
The honest answer: if port 1922 is open on a machine you care about, find out why.
How to Check What's Listening
On Linux/macOS:
On Windows:
The process ID in the output tells you what's using it. Cross-reference with Task Manager or ps aux.
Why Unassigned (and Forgotten) Ports Matter
The registered ports range contains thousands of entries like Tapestry: real IANA assignments for protocols that never achieved widespread adoption. These "registered but dormant" ports matter for a few reasons.
First, they're not truly unassigned. A firewall rule that blocks "unassigned ports" might behave differently from one blocking ports that are "IANA-registered but unused in practice." Security tools need to know the difference.
Second, they're convenient for anything that needs a port number. Because Tapestry is registered but dormant, port 1922 is unlikely to conflict with common software — which makes it attractive for custom applications and, unfortunately, for malware authors who want a port that won't immediately raise flags.
Third, they're a record. The IANA port registry is partly a historical document. Port 1922 tells you that in the early 2000s, someone believed Tapestry was important enough to stake out a port number. They weren't wrong about the research. The deployment just never followed.
此页面对您有帮助吗？