01Astergate Discovery Serviceudp · iana-registered · risk 1/10
UDP port 9106 is assigned to the Astergate Discovery Service, with no widely documented deployment.
port 9106 as Astergate Discovery Service →Port 91062 services
2 entries are registered on port 9106. 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 | |||
|---|---|---|---|---|---|
| :9106 | Astergate Discovery Service | UDP | Network Services | safe | 0 |
| :9106 | Astergate Control Service | TCP | — | safe | 0 |
02Astergate Control Servicetcp · iana-registered · risk 1/10
TCP/9106 is assigned to the Astergate Control Service, with no established common deployment.
port 9106 as Astergate Control Service →filed underNetwork Services
Which one is on your host
The registry says what 9106 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 ':9106\b'- macos
lsof -nP -iTCP:9106 -sTCP:LISTEN- windows
netstat -ano | findstr :9106
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 9106 — 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