2 entries are registered on port 3313. 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 |
|---|---|---|---|---|---|
| :3313 | Verisys FIM | TCP | Security | caution | 5.3k |
| :3313 | Unify Object Broker | TCPUDP | Network Services | safe | 0 |
Verisys is a file integrity monitoring (FIM) software designed to detect unauthorized changes to files and configurations across systems. It is typically employed within enterprise environments to enhance compliance, security, and operational integrity by monitoring critical system files and alerting administrators of any unexpected modifications.
port 3313 as Verisys FIM →TCP and UDP port 3313 is assigned to Unify Object Broker, a service registered to Daegis Inc.
port 3313 as Unify Object Broker →The registry says what 3313 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 ':3313\b'lsof -nP -iTCP:3313 -sTCP:LISTENnetstat -ano | findstr :3313On 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 3313 — 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