2 entries are registered on port 3100. 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 |
|---|---|---|---|---|---|
| :3100 | Tatsoft HTTP Port | TCP | Web Services | caution | 19.4k |
| :3100 | OpCon/xps | TCPUDP | — | safe | 0 |
Port 3100 is primarily utilized by Tatsoft's software suite as its default HTTP listening port for communication. It facilitates interaction between client and server components, enabling users and integrations to interface with Tatsoft applications over a network via standard HTTP protocols.
port 3100 as Tatsoft HTTP Port →TCP/UDP 3100 is assigned to OpCon/xps, but no reliable public protocol or common listener behavior is established.
port 3100 as OpCon/xps →The registry says what 3100 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 ':3100\b'lsof -nP -iTCP:3100 -sTCP:LISTENnetstat -ano | findstr :3100On 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 3100 — 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