Skip to content

OpenSearch — Common Ports

Web & HTTP ServicesReference link ↗

Community software entries: links are references, not individual verification.

Role Unconfirmed (2)

8080
tcpWeb & HTTP Services

8080 is a common alternate HTTP listener, including Tomcat deployments. It is not a universal proxy or framework port; inspect the actual process and configuration.

OpenSearchSearchEngine

9200
tcpEnterprise

Elasticsearch search engine HTTP API port for data indexing and search

OpenSearchHTTP APIPort

Scope

Port associations on this page are community-database references (common usage), not a live measurement of any machine; confirm with the official documentation before deployment.

Frequently asked questions

What port does OpenSearch use?

OpenSearch commonly uses these ports: 8080, 9200. These are community database references — actual configuration may differ.

How do I check if OpenSearch is running?

Run sudo ss -tlpn 'sport = :8080 or sport = :9200' on the server to check for listening processes on these ports. Also use systemctl status <service> to check the service state. Without root you may not see other users' processes. A listening port alone does not prove the software identity — verify with the config file and process name.

What category does OpenSearch belong to?

OpenSearch belongs to the Web & HTTP Services category. This page lists the software's port associations and their roles.

What other ports does OpenSearch use besides the default?

OpenSearch also uses these ports: 8080, 9200. Their purpose (admin interface, metrics, or alternative configuration) is detailed in the role-grouped list above.

Quick Info

Categories
Web & HTTP Services
Associated ports
2
Aliases
—