2 entries are registered on port 8194. 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.
services registered on this number
2 transports in use
entries encrypted on the wire
1 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :8194 | Sophos RMS | TCP | Security | caution | 8.3k |
| :8194 | Bloomberg Open API (BLPAPI) | TCPUDP | Network Services | caution | 0 |
Sophos Remote Management System (RMS) facilitates communication between Sophos endpoint security products and central management consoles. It enables the centralized administration, policy enforcement, status monitoring, and update delivery crucial for maintaining an organization's security infrastructure efficiently.
port 8194 as Sophos RMS →TCP 8194 is commonly used by Bloomberg Terminal and Bloomberg Server API clients to access Bloomberg data.
port 8194 as Bloomberg Open API (BLPAPI) →The registry says what 8194 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.
ss -ltnp | grep ':8194\b'lsof -nP -iTCP:8194 -sTCP:LISTENnetstat -ano | findstr :8194On 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 8194 — 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