# WHATPORT(65310)

## NAME

port 65310 — Unassigned (dynamic/private range) — Unregistered and unnamed — a bare high port with no standard service behind it.

Protocol: TCP  
IANA registry

## DESCRIPTION

65310 falls in the Dynamic/Private range that RFC 6335 sets aside at 49152-65535, which IANA does not assign, so there is no registered service name for it. Nmap's service database lists it as unknown and records it open on about 0.015% of scanned hosts, putting it around 1,250th out of the 8,000-odd TCP ports Nmap tracks. In practice a 65310 you see is almost always an ephemeral client socket — Windows and macOS/BSD allocate outbound source ports from 49152-65535 — or a service someone deliberately parked on an arbitrary high port. Nothing well-documented, and no notable malware, claims it.

## EXPOSURE

**Expose with care.** The port itself carries no verdict; whatever you find listening does. Identify the process before deciding, and do not treat the high number as protection — scanners sweep the full range.

## CHECK

```sh
sudo lsof -nP -iTCP:65310 -sTCP:LISTEN
```

## SEE ALSO

- spec — [RFC 6335 — IANA Procedures for Port Number Registration (Dynamic/Private range 49152-65535)](https://www.rfc-editor.org/rfc/rfc6335.html) (rfc-editor.org)
- source — [nmap-services — Nmap's port frequency database](https://github.com/nmap/nmap/blob/master/nmap-services) (github.com)
- iana — [IANA Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml) (iana.org)

---

HTML: <https://whatport.net/65310/> · JSON: <https://whatport.net/65310.json> · full dataset: <https://whatport.net/ports.json>