01Acctopus Statusudp · iana-registered · risk 1/10
UDP port 6868 is assigned to Acctopus Status, a service registered by Stefan Auweiler.
port 6868 as Acctopus Status →Port 68682 services
2 entries are registered on port 6868. 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.
- entries
- 2
- transport
- udp · tcp
- in transit
- 0/2
- worst risk
- 1/10
services registered on this number
2 transports in use
entries encrypted on the wire
2 of 2 iana-registered
Services on this port
| port | service | risk | |||
|---|---|---|---|---|---|
| :6868 | Acctopus Status | UDP | — | safe | 0 |
| :6868 | Acctopus Command Channel | TCP | — | safe | 0 |
02Acctopus Command Channeltcp · iana-registered · risk 1/10
TCP 6868 is assigned to the Acctopus Command Channel, an obscure service with no documented common deployment.
port 6868 as Acctopus Command Channel →Which one is on your host
The registry says what 6868 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.
- linux
ss -ltnp | grep ':6868\b'- macos
lsof -nP -iTCP:6868 -sTCP:LISTEN- windows
netstat -ano | findstr :6868
On 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 6868 — 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