Port 9200/tcp: Elasticsearch (HTTP REST API)
Category: Databases. Range: registered. Status: de facto standard.
What runs here
The default port for Elasticsearch's HTTP interface, over which clients send REST API calls (indexing, search, cluster management), distinct from port 9300, the transport interface nodes use to talk to each other within a cluster. Notably, IANA's registry does not assign 9200 to Elasticsearch at all. It's officially registered to 'wap-wsp' (WAP connectionless session service), a legacy mobile-carrier protocol; 9200 is purely an Elastic-chosen application default, not an IANA assignment, in the same way 1521 is Oracle's de facto (not official) port.
Why it matters
Elasticsearch has historically shipped without authentication enabled by default in many self-managed deployments, and internet-exposed clusters have repeatedly been found, indexed, and either exfiltrated or wiped with a ransom note: the same pattern seen against exposed MongoDB. Because the entire API surface (including deleting indices) is reachable over plain HTTP once auth is off, a DFIR analyst finding 9200 open to the internet should treat it as equivalent to an open, unauthenticated database until proven otherwise.
Where you see it
Legitimately: Kibana and application clients issuing REST queries, Logstash/Beats ingest traffic, and cluster health checks. Anomalously/maliciously: unauthenticated requests from the internet enumerating indices (GET /_cat/indices) followed by bulk DELETE calls or a newly created index containing a ransom message.
What to look for
| Signal | What it means |
|---|---|
| Unauthenticated /_cluster or /_cat access | Successful, unauthenticated calls to cluster/index management endpoints from an external IP confirm the instance has no security layer (X-Pack security / xpack.security.enabled) active. |
| Mass index deletion | A burst of DELETE requests against multiple indices in quick succession, especially followed by creation of a single new index, matches the pattern of the mass ransom-wipe campaigns targeting exposed Elasticsearch clusters. |