2 entries are registered on port 2599. 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.
services registered on this number
2 transports in use
entries encrypted on the wire
1 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :2599 | SonicWALL Antispam | TCP | caution | 8.8k | |
| :2599 | Snap Discovery | TCPUDP | Network Services | safe | 0 |
Port 2599 is utilized by SonicWALL's Antispam service for communication between the Remote Analyzer (RA) and the Control Center (CC). This dedicated connection enables real-time transfer of spam analysis data, updates, and coordination commands, facilitating effective centralized spam filtering across distributed email environments.
port 2599 as SonicWALL Antispam →TCP/UDP 2599 is assigned to Snap Discovery, a little-documented service with no known common deployment.
port 2599 as Snap Discovery →The registry says what 2599 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.
ss -ltnp | grep ':2599\b'lsof -nP -iTCP:2599 -sTCP:LISTENnetstat -ano | findstr :2599On 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 2599 — 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