01SVDRP Discoveryudp · iana-registered · risk 2/10
UDP discovery for finding Video Disk Recorder (VDR) instances on a local network.
port 6419 as SVDRP Discovery →Port 64192 services
2 entries are registered on port 6419. 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
- 7/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 | |||
|---|---|---|---|---|---|
| :6419 | SVDRP Discovery | UDP | Network Services | safe | 0 |
| :6419 | Simple VDR Protocol (SVDRP) | TCP | Network Services | risk | 0 |
02Simple VDR Protocol (SVDRP)tcp · iana-registered · risk 7/10
SVDRP is VDR's cleartext TCP control protocol for managing digital-TV recordings, channels, timers, and recorder functions.
port 6419 as Simple VDR Protocol (SVDRP) →Which one is on your host
The registry says what 6419 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 ':6419\b'- macos
lsof -nP -iTCP:6419 -sTCP:LISTEN- windows
netstat -ano | findstr :6419
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 6419 — 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