What This Port Is
Port 3379 sits in the registered port range, the band from 1024 to 49151 that IANA manages for services that have applied for an official assignment. Unlike the well-known ports below 1024, registered ports don't require elevated privileges to use. They're the middle tier: not system-reserved, but not randomly claimed either.
Port 3379 has a registration. The service is called SOCORFS, assigned on both TCP and UDP. The registrant is listed as Hugo Charbonneau.
The description IANA provides for SOCORFS is: SOCORFS.
That's the whole entry. The acronym doesn't expand anywhere in the public record. No RFC exists. No technical documentation is indexed anywhere online. The port has a name, a registrant, and no explanation. 1
What the Registered Port Range Means
When someone registers a port with IANA, they're staking a claim — saying "this is mine, don't use it for other things." In the well-known port range (0–1023), that claim comes with documentation, RFCs, and implementation history. In the registered range, the bar is lower. A registration can be as sparse as a name and a contact.
Most registered ports with active use have at least some documentation trail — a product manual, a firewall rule reference, an open-source repository. SOCORFS has none of that. In practice, port 3379 behaves like an unassigned port: nothing is listening there by default, and no common software opens it.
What Might Actually Be on This Port
If you see traffic on port 3379 on your network, it's almost certainly one of three things:
- Scanner noise — automated tools probe all registered ports looking for open services
- Custom software — an application that chose this port precisely because it's quiet and unreserved in practice
- Nothing — the port is closed and the traffic is a probe that got no response
There's no known malware family associated with port 3379, and no CVEs reference it. It's obscure enough that it doesn't appear in most firewall rule templates.
How to Check What's Listening
On Linux or macOS:
On Windows:
If nothing returns, nothing is listening. If something returns, the process name or PID will tell you what claimed it.
Why Unassigned (or Effectively Unassigned) Ports Matter
The registered port range has 48,128 ports. Most of them are either genuinely unassigned or registered in name only, like 3379. This matters for two reasons.
First, it means the port space is large enough that any application can find quiet real estate. A developer building internal tooling can park it on 3379 and rarely collide with anything.
Second, it means the IANA registry is not a guarantee of documentation. A port can be "registered" and still tell you nothing. The registry is a reservation system, not a library. Showing up in the registry means someone claimed it. It doesn't mean they explained it.
Esta página foi útil?