# WHATPORT(52673)

## NAME

port 52673 — Unassigned (dynamic range) — No registered service — it is on scans only because Nmap probes it by default.

Protocol: TCP  
IANA registry

## DESCRIPTION

52673 sits in the Dynamic/Private range (49152-65535), which RFC 6335 sets aside for local and ephemeral use and where IANA assigns nothing. Nmap's nmap-services file lists it as "unknown" with an observed-open frequency of 0.000228, which is enough to keep it inside the default top-1000 TCP set that a bare `nmap TARGET` scans. No public service database names an application here — SANS ISC also shows the service field empty. In practice a hit is either an ephemeral client socket caught mid-connection or a program that was told to bind a high port.

## EXPOSURE

**Expose with care.** You cannot rate a port you cannot name. Identify the owning process locally before deciding anything; an unidentified listener on a public IP should be closed until it is identified.

## CHECK

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

## SEE ALSO

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

---

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