2 entries are registered on port 3017. 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 |
|---|---|---|---|---|---|
| :3017 | Miralix IVR & Voicemail | TCP | Network Services | caution | 11.5k |
| :3017 | Event Listener | TCPUDP | System | safe | 0 |
Port 3017 is primarily associated with Miralix Interactive Voice Response (IVR) and Voicemail services, facilitating voice message handling, automated call routing, and integration with telephony systems to enhance communication workflows within organizations.
port 3017 as Miralix IVR & Voicemail →Historic TCP/UDP assignment for an event-listening service; no standard protocol behavior is documented.
port 3017 as Event Listener →The registry says what 3017 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 ':3017\b'lsof -nP -iTCP:3017 -sTCP:LISTENnetstat -ano | findstr :3017On 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 3017 — 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