# WHATPORT(64623)

## NAME

port 64623 — Unassigned (dynamic range) — Unregistered, but common enough in Nmap's corpus to make every default scan.

Protocol: TCP  
IANA registry

## DESCRIPTION

64623 carries no IANA registration, per RFC 6335's rule that the Dynamic/Private range is never assigned. Nmap's nmap-services rates it "unknown" at 0.000760 — high for an unnamed port in this band, on par with 52869 and 55555 — which guarantees its place in the default top-1000 TCP list. Despite that frequency, SANS ISC still shows no service name and no tracked vulnerabilities. Something binds this port often enough to register statistically, and no public source says what.

## EXPOSURE

**Expose with care.** Frequently observed and never identified is not a reassuring combination. Find the process locally rather than assuming it is benign.

## CHECK

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

## SEE ALSO

- spec — [RFC 6335 — Dynamic Ports (49152-65535)](https://www.rfc-editor.org/rfc/rfc6335.html) (rfc-editor.org)
- iana — [IANA port registry — search 64623](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=64623) (iana.org)
- source — [nmap/nmap — nmap-services frequency data](https://github.com/nmap/nmap/blob/master/nmap-services) (github.com)

---

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