3 entries are registered on port 8880. 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 3 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :8880 | CDDB Protocol Alternate | UDP | Network Services | caution | 29.5k |
| :8880 | Windows Media SOAP Connector | TCP | Streaming | caution | 24.3k |
| :8880 | WebSphere SOAP Connector | TCP | Web Services | caution | 24.1k |
Port 8880 is an alternate port traditionally used by the CD DataBase Protocol (CDDBP), which allows music player software to query CD metadata databases such as Gracenote. It typically uses UDP communications, enabling client software to fetch details like album names, artist information, and track listings without direct user input.
port 8880 as CDDB Protocol Alternate →Port 8880 is commonly associated with Windows Media Server's SOAP connector, serving as a control interface between streaming clients and the server. It facilitates the exchange of structured XML data for media management, streaming session control, and service queries. This port streamlines communication between clients and server infrastructure within media streaming networks.
port 8880 as Windows Media SOAP Connector →The WebSphere Application Server uses port 8880 by default to enable SOAP-based communication between clients and the server. This connector facilitates remote management, deployment, and configuration interfaces using SOAP, a common protocol supporting structured information exchange. It primarily assists in integrating administrative tools and automated systems with WebSphere's application management capabilities.
port 8880 as WebSphere SOAP Connector →The registry says what 8880 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 ':8880\b'lsof -nP -iTCP:8880 -sTCP:LISTENnetstat -ano | findstr :8880On 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 3 entries above.
A port number is not a service. Anything may listen on 8880 — 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