{
  "port": 2717,
  "protocol": "both",
  "service": "pn-requester (registered)",
  "oneLiner": "Registered to IANA as PN REQUESTER, with no public protocol documentation behind the name.",
  "whatItIs": "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": {
    "verdict": "careful",
    "note": "An unidentified listener is the problem, not the port — find the process with lsof or ss before deciding anything about exposing it."
  },
  "checkCommand": "sudo lsof -nP -iTCP:2717 -sTCP:LISTEN",
  "links": [
    {
      "title": "IANA Service Name and Transport Protocol Port Number Registry — 2717 (pn-requester)",
      "url": "https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2717",
      "kind": "iana"
    },
    {
      "title": "nmap/nmap — nmap-services (open-frequency data per port)",
      "url": "https://github.com/nmap/nmap/blob/master/nmap-services",
      "kind": "github"
    }
  ],
  "ianaName": "pn-requester"
}