2 entries are registered on port 82. 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 |
|---|---|---|---|---|---|
| :82 | Torpark Control | UDP | Web Services | caution | 11.5k |
| :82 | XFER Utility | TCPUDP | — | safe | 0 |
Port 82 is commonly associated with alternative web service configurations or specialized control functions, such as for proxy networks like Torpark. It is sometimes used for managing Torpark, a privacy-centric portable web browsing system designed to anonymize internet usage by routing traffic over the Tor network.
port 82 as Torpark Control →TCP/UDP port assigned to the XFER Utility, an obscure utility service registered to Thomas M Smith.
port 82 as XFER Utility →The registry says what 82 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 ':82\b'lsof -nP -iTCP:82 -sTCP:LISTENnetstat -ano | findstr :82On 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 82 — 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