01SD-CAPACITYudp · iana-registered · risk 1/10
UDP port 2384 is assigned to the obscure SD-CAPACITY service.
port 2384 as SD-CAPACITY →Port 23842 services
2 entries are registered on port 2384. It is a registered port (1024–49151) — IANA records an assignee, but nothing stops other software from listening here, which is why the number carries more than one entry.
- entries
- 2
- transport
- udp · tcp
- in transit
- 0/2
- worst risk
- 1/10
services registered on this number
2 transports in use
entries encrypted on the wire
2 of 2 iana-registered
Services on this port
| port | service | risk | |||
|---|---|---|---|---|---|
| :2384 | SD-CAPACITY | UDP | — | safe | 0 |
| :2384 | SD-REQUEST | TCP | — | safe | 0 |
02SD-REQUESTtcp · iana-registered · risk 1/10
An unidentified SD-REQUEST service assigned to TCP port 2384.
port 2384 as SD-REQUEST →Which one is on your host
The registry says what 2384 is registered to. What is listening on it right now is decided by the host, and only the host can be asked. Each of these prints the process behind the socket.
- linux
ss -ltnp | grep ':2384\b'- macos
lsof -nP -iTCP:2384 -sTCP:LISTEN- windows
netstat -ano | findstr :2384
On Linux and Windows the process name comes back with the socket; on macOS lsof needs sudo to name a process that isn't yours. Match what it prints against the 2 entries above.
A port number is not a service. Anything may listen on 2384 — what you actually met is decided by the host, not the registry. If a service is missing here, it belongs in the registry.
contribute an entry