01Kerberos 524tcp · udp · iana-registered · risk 4/10
Legacy Kerberos v5-to-v4 ticket conversion service, typically provided by krb524d on TCP/UDP 4444.
port 4444 as Kerberos 524 →Port 44442 services
2 entries are registered on port 4444. 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
- tcp · udp
- 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 | |||
|---|---|---|---|---|---|
| :4444 | Kerberos 524 | TCPUDP | Security | caution | 0 |
| :4444 | NV Video / Metasploit Handler | TCPUDP | Security | risk | 0 |
02NV Video / Metasploit Handlertcp · udp · iana-registered · risk 7/10
IANA assigns 4444 to NV Video, but TCP 4444 is also widely recognized as Metasploit’s default handler port.
port 4444 as NV Video / Metasploit Handler →Which one is on your host
The registry says what 4444 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 ':4444\b'- macos
lsof -nP -iTCP:4444 -sTCP:LISTEN- windows
netstat -ano | findstr :4444
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 4444 — 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