2 entries are registered on port 3864. 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
2 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :3864 | Aggregate Server Access Protocol (ASAP) over SCTP/TLS | SCTPtls | Network Services | safe | 0 |
| :3864 | Aggregate Server Access Protocol over TLS | TCPtls | Network Services | safe | 0 |
TLS-protected SCTP endpoint for ASAP, the RSerPool protocol used to manage server pools and endpoint handlespaces.
port 3864 as Aggregate Server Access Protocol (ASAP) over SCTP/TLS →ASAP over TLS carries Reliable Server Pooling registration and server-pool access traffic over TCP.
port 3864 as Aggregate Server Access Protocol over TLS →The registry says what 3864 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 ':3864\b'lsof -nP -iTCP:3864 -sTCP:LISTENnetstat -ano | findstr :3864On 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 3864 — 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