2 entries are registered on port 530. 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
2 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :530 | RPC | TCPUDP | Network Services | caution | 8.8k |
| :530 | Courier RPC | TCPUDP | Network Services | safe | 0 |
Remote Procedure Call (RPC) enables one program to request a service from a program located on another computer in a network. It abstracts the communication process, making it easier to build distributed, client-server applications because the calling method appears as if it's local despite being remote.
port 530 as RPC →Courier RPC traffic uses TCP or UDP port 530.
port 530 as Courier RPC →The registry says what 530 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 ':530\b'lsof -nP -iTCP:530 -sTCP:LISTENnetstat -ano | findstr :530On 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 530 — 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