2 entries are registered on port 4018. 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
2 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :4018 | Protocol Info & Warnings | TCPUDP | Network Services | caution | 6.7k |
| :4018 | Talarian Mcast | TCPUDP | Network Services | safe | 0 |
Port 4018 is typically associated with services that relay protocol metadata, alerts, or control messages within networked environments. It facilitates the exchange of status updates, notifications, and warnings between devices or applications using various underlying protocols.
port 4018 as Protocol Info & Warnings →IANA assigns TCP and UDP port 4018 to Talarian Mcast, a service whose current use is not established.
port 4018 as Talarian Mcast →The registry says what 4018 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 ':4018\b'lsof -nP -iTCP:4018 -sTCP:LISTENnetstat -ano | findstr :4018On 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 4018 — 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