01ASSIA CloudCheck WiFi Management Keepaliveudp · iana-registered · risk 1/10
UDP port assigned to ASSIA CloudCheck WiFi management keepalives.
port 45514 as ASSIA CloudCheck WiFi Management Keepalive →Port 455142 services
2 entries are registered on port 45514. 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 | |||
|---|---|---|---|---|---|
| :45514 | ASSIA CloudCheck WiFi Management Keepalive | UDP | Network Services | safe | 0 |
| :45514 | ASSIA CloudCheck WiFi Management System | TCP | Network Services | safe | 0 |
02ASSIA CloudCheck WiFi Management Systemtcp · iana-registered · risk 1/10
TCP/45514 is assigned to ASSIA CloudCheck, a Wi-Fi management system; public protocol details are scarce.
port 45514 as ASSIA CloudCheck WiFi Management System →Which one is on your host
The registry says what 45514 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 ':45514\b'- macos
lsof -nP -iTCP:45514 -sTCP:LISTEN- windows
netstat -ano | findstr :45514
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 45514 — 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