2 entries are registered on port 4100. 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 |
|---|---|---|---|---|---|
| :4100 | WatchGuard Auth Applet | Security | caution | 10.1k | |
| :4100 | IGo Incognito Data Port | TCPUDP | — | safe | 0 |
Port 4100 is typically associated with the WatchGuard Authentication Applet, which facilitates user authentication processes within WatchGuard network security devices. This service enables clients to communicate authentication credentials to a WatchGuard firewall or security appliance, granting trusted network access based on identity verification.
port 4100 as WatchGuard Auth Applet →Data traffic port assigned to the IGo Incognito service.
port 4100 as IGo Incognito Data Port →The registry says what 4100 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 ':4100\b'lsof -nP -iTCP:4100 -sTCP:LISTENnetstat -ano | findstr :4100On 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 4100 — 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