01LISA UDP Transfer Channeludp · iana-registered · risk 1/10
UDP port assigned for the LISA UDP Transfer Channel file-transfer service.
port 3487 as LISA UDP Transfer Channel →Port 34872 services
2 entries are registered on port 3487. It is a registered port (1024–49151) — IANA records an assignee, but nothing stops other software from listening here, which is why the number carries more than one entry.
- entries
- 2
- transport
- udp · tcp
- in transit
- 0/2
- worst risk
- 1/10
services registered on this number
2 transports in use
entries encrypted on the wire
2 of 2 iana-registered
Services on this port
| port | service | risk | |||
|---|---|---|---|---|---|
| :3487 | LISA UDP Transfer Channel | UDP | File Transfer | safe | 0 |
| :3487 | LISA TCP Transfer Channel | TCP | — | safe | 0 |
02LISA TCP Transfer Channeltcp · iana-registered · risk 1/10
TCP/3487 is assigned to the LISA TCP Transfer Channel, but no registered holder or widely documented deployment is known.
port 3487 as LISA TCP Transfer Channel →filed underFile Transfer
Which one is on your host
The registry says what 3487 is registered to. What is listening on it right now is decided by the host, and only the host can be asked. Each of these prints the process behind the socket.
- linux
ss -ltnp | grep ':3487\b'- macos
lsof -nP -iTCP:3487 -sTCP:LISTEN- windows
netstat -ano | findstr :3487
On Linux and Windows the process name comes back with the socket; on macOS lsof needs sudo to name a process that isn't yours. Match what it prints against the 2 entries above.
A port number is not a service. Anything may listen on 3487 — what you actually met is decided by the host, not the registry. If a service is missing here, it belongs in the registry.
contribute an entry