Port 28093 services

3 entries are registered on port 2809. 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.

entries: 3
transport: tcp · udp
in transit: 0/3
worst risk: 6/10

Services on this port

ranked by lookups

port	service	proto	category	risk	views
:2809	IBM WebSphere WAS Bootstrap RMI	TCP	Web Services	caution	10.9k
:2809	CORBA IIOP URL	TCP	Network Services	caution	7.5k
:2809	CORBA Naming Service	TCPUDP	Network Services	risk	0

01IBM WebSphere WAS Bootstrap RMItcp · unofficial · risk 4/10

Port 2809 is primarily used by IBM WebSphere Application Server (WAS) for its bootstrap and Remote Method Invocation (RMI) default communications. It allows Java clients and other middleware to connect to the WebSphere server for enterprise Java applications' initialization, remote procedure calls, and distributed object management. As a key component in enterprise middleware infrastructure, this port plays a critical role in establishing connections with WebSphere services, aiding in the deployment, management, and interaction with Java EE applications.

port 2809 as IBM WebSphere WAS Bootstrap RMI →

02CORBA IIOP URLtcp · iana-registered · risk 4/10

Port 2809 is officially designated for CORBA's corbaloc IIOP URL, following the CORBA 3.0.3 specification. It enables client applications to locate CORBA objects using Inter-ORB Protocol (IIOP), facilitating standardized distributed object communication across heterogeneous networks and platforms.

port 2809 as CORBA IIOP URL →

03CORBA Naming Servicetcp · udp · iana-registered · risk 6/10

CORBA Naming Service and IIOP object references commonly use port 2809.

port 2809 as CORBA Naming Service →

filed underWeb Services Cloud Network Services System

Which one is on your host

ask the machine, not the registry

The registry says what 2809 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.

linux: ss -ltnp | grep ':2809\b'
macos: lsof -nP -iTCP:2809 -sTCP:LISTEN
windows: netstat -ano | findstr :2809

On 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 3 entries above.

A port number is not a service. Anything may listen on 2809 — 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

Port :28093 services