01StorMagic Cluster Servicestcp · iana-registered · risk 1/10
StorMagic Cluster Services for clustered storage deployments.
port 4174 as StorMagic Cluster Services →Port 41742 services
2 entries are registered on port 4174. 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
- tcp · udp
- 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 | |||
|---|---|---|---|---|---|
| :4174 | StorMagic Cluster Services | TCP | System | safe | 0 |
| :4174 | StorMagic Discovery | UDP | Network Services | safe | 0 |
02StorMagic Discoveryudp · iana-registered · risk 1/10
UDP port assigned to StorMagic Discovery, a StorMagic service; public protocol and deployment details are limited.
port 4174 as StorMagic Discovery →Which one is on your host
The registry says what 4174 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 ':4174\b'- macos
lsof -nP -iTCP:4174 -sTCP:LISTEN- windows
netstat -ano | findstr :4174
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 4174 — 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