2 entries are registered on port 370. It is a well-known port (0–1023) — assignments here are IANA's, and a service found on one is usually the service that was assigned it.
services registered on this number
2 transports in use
entries encrypted on the wire
0 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :370 | SecureCast | TCPUDP | Security | caution | 10.0k |
| :370 | CodaAuth2 Authentication | TCPUDP | Security | caution | 8.9k |
SecureCast is a protocol primarily used for outbound communication with Network Associates Inc. (NAI) servers. It facilitates the secure management, monitoring, and transfer of systems or security-related data, serving enterprise network infrastructure and security services. This port is often used by administration tools or security applications to transmit information externally.
port 370 as SecureCast →CodaAuth2 operates as the authentication service within the Coda distributed filesystem, facilitating secure identity verification and access control for networked file sharing. It enables clients and servers to establish trust, supporting seamless collaboration and data access in Coda environments.
port 370 as CodaAuth2 Authentication →The registry says what 370 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 ':370\b'lsof -nP -iTCP:370 -sTCP:LISTENnetstat -ano | findstr :370On 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 370 — 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