Port 111/tcp/udp: RPCbind (Portmapper) / ONC RPC
Category: File Sharing & Remote Access. Range: well-known. Status: iana registered.
What runs here
The ONC RPC (Sun RPC) directory service: it maps an RPC program number (such as the NFS mount/nfsd services) to the actual dynamic port that service is listening on, functionally the Unix/Linux counterpart to the Windows MSRPC endpoint mapper on port 135. Current implementations use the rpcbind protocol (RFC 1833); the older, TCP/UDP-specific predecessor was the Port Mapper protocol.
Why it matters
An exposed rpcbind is a reconnaissance goldmine: an rpcinfo -p query against it dumps every RPC service registered on the host along with its live port, effectively mapping the box's RPC attack surface for free. UDP port 111 is also a well-documented DDoS reflection/amplification vector: a small spoofed query can trigger a substantially larger response directed at a victim whose address was forged as the source.
Where you see it
Legitimately: an NFS server (or other ONC RPC service) registering itself on startup, or a local client resolving an RPC service's port. Anomalously/maliciously: rpcinfo -p enumeration of an internet-facing host, or abuse of an open UDP/111 service as a DDoS reflector against a spoofed victim IP.
What to look for
| Signal | What it means |
|---|---|
| rpcinfo enumeration | Unsolicited RPC program-number queries from unfamiliar source IPs are a straightforward reconnaissance signal. |
| Amplification traffic pattern | A burst of small inbound UDP/111 queries paired with disproportionately larger outbound responses to a third-party IP indicates the host is being abused as a DDoS reflector. |
In practice
A burst of small inbound UDP/111 queries followed by disproportionately larger outbound responses toward a third-party IP that never initiated the query is the signature of the host being abused as a DDoS reflector, not a real client lookup.
Related ports
- 2049/tcp/udp: NFS (Network File System)