No registration and no known default service — but it sits inside the Kubernetes NodePort range.
IANA leaves 30951 unassigned; it falls in the 30940–30998 unassigned block. No well-known software binds it by default and Nmap's frequency table lists it as unknown with a very low hit rate. The one systematic reason it appears is Kubernetes: the default NodePort range is 30000–32767, and the apiserver allocates ports from it more or less arbitrarily, so any NodePort Service can land here. Otherwise an open 30951 is an application that was handed a free port.
Expose with care
Nothing standard lives here, so the verdict belongs to whatever answers — fingerprint it before deciding, and treat a NodePort as an unintentionally public path to a cluster Service.
$ nc -vz -w 3 TARGET 30951Seen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.