3 entries are registered on port 6112. 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 |
|---|---|---|---|---|---|
| :6112 | Battle.net Gaming | TCP | Gaming | caution | 13.6k |
| :6112 | DTSPCD | TCPUDP | Remote Access | caution | 10.4k |
| :6112 | Club Penguin Server | TCP | Gaming | caution | 9.0k |
Port 6112 is predominantly used for Blizzard's Battle.net gaming service, facilitating multiplayer matchmaking, real-time communication, and game data synchronization. It also serves similar functions for other popular gaming platforms such as ArenaNet and Relic, enabling seamless online gameplay and connectivity between gamers around the world.
port 6112 as Battle.net Gaming →DTSPCD (Distributed Terminal Server Process Controller Daemon) is a network service primarily used to remotely execute commands and launch applications on UNIX systems, notably those running CDE (Common Desktop Environment). It facilitates client-server interactions for remote desktop management, enabling administrative tasks and remote application control over a network. While originally designed to enhance remote system management capabilities, it has since fallen out of favor due to significant security vulnerabilities.
port 6112 as DTSPCD →Port 6112 is commonly associated with the online multiplayer game Club Penguin, a Disney-branded virtual world for kids that was active from 2005 to 2017. It facilitated player connections, allowing children to interact in a safe virtual environment, engage in mini-games, and participate in various in-world activities. The port primarily supported the game's client-server architecture to enable seamless gameplay and chat communication.
port 6112 as Club Penguin Server →The registry says what 6112 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 ':6112\b'lsof -nP -iTCP:6112 -sTCP:LISTENnetstat -ano | findstr :6112On 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 6112 — 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