# WHATPORT(1007)

## NAME

port 1007 — Unassigned — Unassigned at IANA with no conventional service; whatever is listening picked the number itself.

Protocol: TCP  
IANA registry

## DESCRIPTION

IANA's registry leaves 1002–1007 unassigned, and nmap lists 1007/tcp as unknown with one of the lowest open-frequency scores in this range. There is no protocol to expect and no scanner label to lean on. What it does tell you: 1007 is inside the system port range defined by RFC 6335, so on a Unix-like host a process needed root to bind it, and something privileged is answering. That is the interesting part, and it is worth chasing down.

## EXPOSURE

**Expose with care.** An unnamed, privileged listener is exactly the thing to identify before allowing it through a firewall — the registry gives you no cover here.

## CHECK

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

## SEE ALSO

- iana — [IANA Service Name and Transport Protocol Port Number Registry (1002–1007 unassigned)](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml) (iana.org)
- spec — [RFC 6335 — IANA procedures and the System (0–1023) port range](https://www.rfc-editor.org/rfc/rfc6335.html) (rfc-editor.org)
- source — [nmap-services (1007/tcp unknown)](https://github.com/nmap/nmap/blob/master/nmap-services) (github.com)

---

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