2 entries are registered on port 760. 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 |
|---|---|---|---|---|---|
| :760 | Kerberos Registration | TCPUDP | Security | safe | 6.0k |
| :760 | Name Service | TCPUDP | Network Services | caution | 5.6k |
Port 760 is utilized by the Kerberos registration service (known as krbupdate or kreg). It facilitates the registration and update of Kerberos principals and credentials, enabling centralized identity management and secure authentication within a networked environment.
port 760 as Kerberos Registration →Port 760, associated with the 'ns' service, typically refers to the UNIX-based Name Server (ns), a legacy RPC-based protocol used for name and directory service purposes. Once more common in UNIX environments, this port now sees minimal use but can still be found in some older networks or custom deployments. It facilitates network-based lookups of naming information, operating over both TCP and UDP transports.
port 760 as Name Service →The registry says what 760 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 ':760\b'lsof -nP -iTCP:760 -sTCP:LISTENnetstat -ano | findstr :760On 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 760 — 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