2 entries are registered on port 5312. 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 |
|---|---|---|---|---|---|
| :5312 | Ginever.net Data Port | TCPUDP | Gaming | caution | 7.2k |
| :5312 | Permabit Client-Server | TCPUDP | — | safe | 0 |
Port 5312 is primarily used by Ginever.net's services for data communication between clients and their gaming and chat platform servers. It facilitates the transfer of gameplay data, messaging, and coordination traffic necessary to maintain interactive, networked experiences.
port 5312 as Ginever.net Data Port →TCP and UDP port 5312 is assigned to Permabit Client-Server; deployments and protocol details are not established.
port 5312 as Permabit Client-Server →The registry says what 5312 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 ':5312\b'lsof -nP -iTCP:5312 -sTCP:LISTENnetstat -ano | findstr :5312On 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 5312 — 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