01eQ-3 Discovery and Configurationudp · iana-registered · risk 1/10
UDP port assigned for eQ-3 device discovery and configuration.
port 43439 as eQ-3 Discovery and Configuration →Port 434392 services
2 entries are registered on port 43439. 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 | |||
|---|---|---|---|---|---|
| :43439 | eQ-3 Discovery and Configuration | UDP | IoT | safe | 0 |
| :43439 | eQ-3 Firmware Update | TCP | IoT | safe | 0 |
02eQ-3 Firmware Updatetcp · iana-registered · risk 1/10
IANA assigns TCP/43439 to eQ-3 firmware updates; it has not been observed open in the cited internet-wide scan data.
port 43439 as eQ-3 Firmware Update →filed underIoT
Which one is on your host
The registry says what 43439 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 ':43439\b'- macos
lsof -nP -iTCP:43439 -sTCP:LISTEN- windows
netstat -ano | findstr :43439
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 43439 — 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