2 entries are registered on port 5031. 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 |
|---|---|---|---|---|---|
| :5031 | AVM CAPI-over-TCP | TCPUDP | Network Services | caution | 12.0k |
| :5031 | Direct Message Protocol | UDP | — | safe | 0 |
AVM CAPI-over-TCP enables ISDN signaling data to be transmitted over Ethernet networks, effectively encapsulating ISDN protocols within TCP/IP for remote access or integration. This facilitates the bridging of traditional ISDN communication with modern IP infrastructure, often serving AVM's Fritz!Box devices and similar hardware.
port 5031 as AVM CAPI-over-TCP →UDP port 5031 is assigned to the Direct Message Protocol, but no established public deployment is known.
port 5031 as Direct Message Protocol →The registry says what 5031 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 ':5031\b'lsof -nP -iTCP:5031 -sTCP:LISTENnetstat -ano | findstr :5031On 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 5031 — 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