01Logstash Beatstcp · unofficial · risk 6/10
Default TCP port for Logstash receiving events from Beats such as Filebeat.
port 5044 as Logstash Beats →Port 50442 services
2 entries are registered on port 5044. 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
- 6/10
services registered on this number
2 transports in use
entries encrypted on the wire
1 of 2 iana-registered
Services on this port
| port | service | risk | |||
|---|---|---|---|---|---|
| :5044 | Logstash Beats | TCP | Security | risk | 0 |
| :5044 | LXI Event Service | TCPUDP | Network Services | safe | 0 |
02LXI Event Servicetcp · udp · iana-registered · risk 2/10
LXI instruments use this service to exchange LAN events and coordinate triggers across test equipment.
port 5044 as LXI Event Service →Which one is on your host
The registry says what 5044 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 ':5044\b'- macos
lsof -nP -iTCP:5044 -sTCP:LISTEN- windows
netstat -ano | findstr :5044
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 5044 — 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