Port 9095Unassigned Port
TCP and UDP port 9095 have no registered IANA service assignment.
- transport
- unknown
- in transit
- cleartext
- assignment
- unofficial
- risk
- 0/10
- lookups
- 0
single transport
payload readable on path
used by convention
safe
rank 994 of 2,308 · top 43%
Technical Details
what runs on :9095IANA assigns no service name or transport protocol to port 9095. There is therefore no standard handshake, framing, encryption behavior, or related protocol defaults to document.
Security Information
exposure of :9095risk score
0/ 10safe
routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
unknown
every listening transport is another surface to filter at the edge
security overview
An unassigned port is not inherently safe or unsafe; risk depends entirely on the application listening there. Do not expose it to the internet without identifying the service and applying that service's authentication and access controls.
Related Ports
ports registered around :9095, by lookups.
| port | service | risk | |||
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :9080 | WebSphere HTTP Transport (default) | TCP | Web Services | caution | 51.6k |
| :9090 | Openfire Admin Console | TCP | Web Services | caution | 34.2k |
| :9091 | Openfire Admin Console (SSL) | TCPtls | Web Services | caution | 28.3k |
| :9043 | WebSphere Admin Console (SSL) | TCP | Web Services | caution | 28.0k |
| :9090 | McAfee Web Gateway Proxy | TCPtls | Web Services | caution | 24.3k |
| :9060 | WebSphere Admin Console | TCP | Web Services | caution | 23.0k |
| :9105 | Xadmin Control Daemon | TCPUDP | Remote Access | caution | 19.9k |
risk mix of the 8 listed
- caution100%
2 of 8 encrypted