2 entries are registered on port 652. It is a well-known port (0–1023) — assignments here are IANA's, and a service found on one is usually the service that was assigned it.
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 |
|---|---|---|---|---|---|
| :652 | DTCP | TCP | Security | caution | 5.6k |
| :652 | HELLO_PORT | TCPUDP | — | safe | 0 |
Dynamic Tunnel Configuration Protocol (DTCP) facilitates the dynamic establishment, maintenance, and termination of network tunnels such as VPNs, enabling efficient, flexible, and automated secure communication channels within large or complex networks.
port 652 as DTCP →A TCP/UDP service assignment for HELLO_PORT; no public protocol behavior is documented.
port 652 as HELLO_PORT →The registry says what 652 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 ':652\b'lsof -nP -iTCP:652 -sTCP:LISTENnetstat -ano | findstr :652On 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 652 — 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