Port 2362: Unassigned — A Gap in the Registry

What Port 2362 Is

Port 2362 is unassigned. The Internet Assigned Numbers Authority (IANA), which maintains the official registry of port-to-service mappings, has not allocated this port to any named protocol or application. ¹

It sits in the registered port range (1024–49151), the middle tier of the port numbering system.

The Registered Port Range

Ports divide into three tiers:

• Well-known ports (0–1023): Reserved for foundational protocols. HTTP gets 80, HTTPS gets 443, SSH gets 22. These require IANA approval and root privileges to bind.
• Registered ports (1024–49151): Where applications go to claim a number. Any software vendor can apply to IANA to have a port number officially registered to their service. This is where port 2362 lives.
• Dynamic/ephemeral ports (49152–65535): Not registered to anything. Used temporarily by operating systems for outbound connections.

Port 2362 being unassigned in the registered range means no vendor has successfully registered it. It's a gap — a number that exists in the registry with no name attached.

What You'll Read Elsewhere

Several third-party port databases list port 2362 as used by "Microsoft SharePoint Services" for SOAP-based administration traffic. Trace this claim to its source and it evaporates. No Microsoft documentation confirms that SharePoint uses port 2362, and the IANA registry contains no such entry. The most likely explanation: one site made an incorrect association years ago, and dozens of others copied it. Port databases do this constantly.

If you're seeing traffic on port 2362 in a SharePoint environment, it's worth investigating your specific configuration rather than trusting a third-party list.

If You See Traffic on Port 2362

Port 2362 can be used by any application that needs a port. There's no formal claim on it, so developers sometimes use unassigned ports for custom services, internal tooling, or legacy applications that predate IANA registration.

To see what's actually listening on port 2362 on your system:

macOS / Linux:

# Check what process is listening on port 2362
sudo lsof -i :2362

# Alternative with netstat
sudo netstat -tlnp | grep 2362

Windows:

# Show all listening ports with process IDs
netstat -ano | findstr :2362

# Then look up the process by PID
tasklist | findstr <PID>

If nothing appears, nothing is using it. If something does appear, the process name will tell you more than any port database will.

Why Unassigned Ports Matter

The port system works because assignments create predictability. When you connect to port 443, you know you'll get HTTPS. When your firewall sees traffic on port 22, it knows to treat it as SSH. This predictability is what allows firewalls, intrusion detection systems, and network monitoring tools to reason about traffic.

Unassigned ports break this predictability — in both directions. Legitimate software uses them for custom services. Malware uses them to avoid blocking rules that target well-known ports. An unassigned port in your firewall logs is a question mark that deserves an answer.

Port 2362 is one of thousands of unassigned numbers in the registered range. Most will never be claimed. A few will eventually be registered as some new protocol needs a home. For now, 2362 is empty space in the registry — available, unclaimed, and occasionally borrowed by whatever needs a port with no prior obligations.