PORT 9200 / TCPDatabase & CacheExposure Risk: Critical
Port 9200: Elasticsearch — Elasticsearch REST HTTP API
Primary HTTP port for Elasticsearch search and analytics engine queries.
Default Service
Elasticsearch
Process: java (elasticsearch)
Transport Protocol
TCP
IANA Registered Port 9200
Docker Port Flag
-p 9200:9200
Container to Host Mapping
How to Check & Kill Process on Port 9200 (EADDRINUSE Fix)
macOS & Linux (lsof / kill)
# Find process using port 9200 sudo lsof -i :9200 # Instantly kill process on port 9200 lsof -ti:9200 | xargs kill -9
Windows (PowerShell & CMD)
# Find PID listening on port 9200 netstat -ano | findstr :9200 # Force kill by PID taskkill /PID <PID_NUMBER> /F
Cross-Platform Node.js One-Liner
# Kill port 9200 via npx npx kill-port 9200 # Or diagnose via Castov CLI npx castov fix "EADDRINUSE :::9200"
Linux Firewall (UFW) & Connectivity Test
# Test if port 9200 is reachable nc -zv localhost 9200 # Allow or deny port 9200 in UFW sudo ufw allow 9200/tcp
Frequently Asked Questions about Port 9200
What is Port 9200 used for?
Port 9200 is the standard network port for Elasticsearch (Elasticsearch REST HTTP API) operating over TCP. The typical system daemon or process is java (elasticsearch).
How do I kill a process running on Port 9200 (EADDRINUSE)?
On macOS and Linux, run: lsof -ti:9200 | xargs kill -9 (or npx kill-port 9200). On Windows PowerShell/CMD, run: netstat -ano | findstr :9200 and then taskkill /PID <PID> /F.
Is it safe to expose Port 9200 to the internet?
Port 9200 has a Critical security risk profile. Primary HTTP port for Elasticsearch search and analytics engine queries.