2 entries are registered on port 90. 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
1 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :90 | DNSIX | TCPUDP | Security | safe | 16.1k |
| :90 | PointCast | TCPUDP | Web Services | caution | 9.4k |
DNSIX (DoD Network Security for Information Exchange) facilitates secure attribute-based access control within Department of Defense networks, enabling attribute token mapping to govern data exchange securely across interconnected systems.
port 90 as DNSIX →PointCast was an early push technology service prominent in the late 1990s, which delivered personalized news and information to users' desktops over the internet, typically via a screensaver interface. It relied heavily on port 90 for communication, using both TCP and UDP protocols to transfer data streams and content updates.
port 90 as PointCast →The registry says what 90 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 ':90\b'lsof -nP -iTCP:90 -sTCP:LISTENnetstat -ano | findstr :90On 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 90 — 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