2 entries are registered on port 3003. 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 |
|---|---|---|---|---|---|
| :3003 | Miralix GreenBox API | TCP | Remote Access | caution | 10.6k |
| :3003 | CGMS | TCPUDP | — | safe | 0 |
Miralix GreenBox API is a communication interface designed to integrate Miralix’s telephony and contact center solutions with external systems and business tools. It streamlines the process of connecting call control, presence information, and other unified communications features, enabling organizations to optimize customer interactions and internal communications through a centralized API platform.
port 3003 as Miralix GreenBox API →CGMS is an obscure service assigned to TCP and UDP port 3003; its protocol is not documented in the registry.
port 3003 as CGMS →The registry says what 3003 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 ':3003\b'lsof -nP -iTCP:3003 -sTCP:LISTENnetstat -ano | findstr :3003On 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 3003 — 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