01Remote Server Control and Test Serviceudp · iana-registered · risk 1/10
UDP/10201 is assigned to the Remote Server Control and Test Service, with no commonly deployed listener documented.
port 10201 as Remote Server Control and Test Service →Port 102012 services
2 entries are registered on port 10201. 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 | |||
|---|---|---|---|---|---|
| :10201 | Remote Server Control and Test Service | UDP | Network Services | safe | 0 |
| :10201 | Remote Server Management Service | TCP | Remote Access | safe | 0 |
02Remote Server Management Servicetcp · iana-registered · risk 1/10
TCP/10201 is assigned to the Remote Server Management Service, with no established common deployment.
port 10201 as Remote Server Management Service →Which one is on your host
The registry says what 10201 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 ':10201\b'- macos
lsof -nP -iTCP:10201 -sTCP:LISTEN- windows
netstat -ano | findstr :10201
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 10201 — 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