# WHATPORT(2717)

## NAME

port 2717 — pn-requester (registered) — Registered to IANA as PN REQUESTER, with no public protocol documentation behind the name.

Protocol: TCP/UDP  
IANA: pn-requester

## DESCRIPTION

IANA lists 2717 for both TCP and UDP as pn-requester, "PN REQUESTER", with 2718 registered as pn-requester2. No specification, vendor documentation, or open implementation of the protocol is publicly available. Nmap carries the registered name and gives 2717 an unusually high open-frequency for an obscure port (about 0.33% of scanned hosts), which means something answers there in the wild — but nothing public identifies what. Treat a listener on 2717 as unidentified software until you fingerprint it locally.

## EXPOSURE

**Expose with care.** An unidentified listener is the problem, not the port — find the process with lsof or ss before deciding anything about exposing it.

## CHECK

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

## SEE ALSO

- iana — [IANA Service Name and Transport Protocol Port Number Registry — 2717 (pn-requester)](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2717) (iana.org)
- source — [nmap/nmap — nmap-services (open-frequency data per port)](https://github.com/nmap/nmap/blob/master/nmap-services) (github.com)

---

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