2 entries are registered on port 1313. 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 |
|---|---|---|---|---|---|
| :1313 | Xbiim Canvii Server | TCP | Web Services | caution | 12.4k |
| :1313 | BMC PATROLDB | TCPUDP | Databases | safe | 0 |
Port 1313 is primarily associated with the Xbiim service, specifically the Canvii server, which facilitates multimedia content distribution, interactive media applications, or custom data transfers for specialized environments.
port 1313 as Xbiim Canvii Server →Historic alias for the BMC PATROLDB service on TCP and UDP port 1313.
port 1313 as BMC PATROLDB →The registry says what 1313 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 ':1313\b'lsof -nP -iTCP:1313 -sTCP:LISTENnetstat -ano | findstr :1313On 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 1313 — 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