# WHATPORT(10626)

## NAME

port 10626 — Unassigned — No IANA assignment and no established use; the honest answer is that nobody owns this port.

Protocol: TCP  
IANA registry

## DESCRIPTION

IANA lists 10626 as unassigned, and Nmap's `nmap-services` — which is built from real internet scan data — has it as `unknown` at a very low hit rate. No documented application, appliance, or backdoor defaults to it. If you found it on a scan, the source is a locally chosen port: an application config, a Docker `-p` mapping, or a service that increments off a base port and landed here.

## EXPOSURE

**Expose with care.** Nothing about the number makes it safe or unsafe. The verdict belongs to whatever service you find bound to it.

## CHECK

```sh
nmap -Pn -sV -p 10626 TARGET
```

## SEE ALSO

- 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/10626/> · JSON: <https://whatport.net/10626.json> · full dataset: <https://whatport.net/ports.json>