# WHATPORT(9090)

## NAME

port 9090 — Prometheus, Cockpit — Prometheus's web UI and API by default, and Cockpit's web console on Linux servers — two very different things on one number.

Protocol: TCP  
IANA: websm

## DESCRIPTION

A fresh Prometheus serves its status page and HTTP API on 9090, so on a monitoring host that is almost certainly what it is. On a Linux server it is at least as likely to be Cockpit, whose web console is reached at https://host:9090 and which logs you in with system credentials. IANA registers 9090 as websm (IBM Web-based System Manager). Tell them apart by whether the port speaks TLS and what the root path returns.

## EXPOSURE

**Expose with care.** Cockpit is designed to be reached over HTTPS with real logins; Prometheus is not — it has no authentication out of the box and its API exposes every metric you collect, so put it behind a proxy or Prometheus's own web config.

## CHECK

```sh
curl -sI http://TARGET:9090/
```

## SEE ALSO

- docs — [Prometheus — getting started (status page on localhost:9090)](https://prometheus.io/docs/prometheus/latest/getting_started/) (prometheus.io)
- docs — [Cockpit — running Cockpit (https://ip:9090)](https://cockpit-project.org/running.html) (cockpit-project.org)
- source — [prometheus/prometheus on GitHub](https://github.com/prometheus/prometheus) (github.com)
- iana — [IANA Service Name and Transport Protocol Port Number Registry — 9090](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=9090) (iana.org)

---

HTML: <https://whatport.net/9090/> · JSON: <https://whatport.net/9090.json> · full dataset: <https://whatport.net/ports.json>