Port 5601 is Kibana (and OpenSearch Dashboards), the web interface for searching and visualising Elasticsearch data. It should not be reachable from the public internet.
- Port
- 5601
- Protocol
- TCP
- Service
- Kibana
- Expose to internet?
- No
- Also used by
- Kibana, OpenSearch Dashboards
Is port 5601 safe to open?
Kibana shows whatever is in Elasticsearch, often application logs with personal data, tokens and internal hostnames. Without security enabled on the cluster, it has no login at all. Older Kibana releases have also had remote code execution flaws.
How to secure Kibana
- Enable Elasticsearch security so Kibana requires a login (default in Elasticsearch 8).
- Bind Kibana to localhost (
server.host: "localhost"in kibana.yml) and publish it through a proxy with TLS. - Keep Kibana on the same supported version as Elasticsearch.
Check if port 5601 is open
Linux: what is listening on this port
sudo ss -tlpn | grep ':5601 'Windows (PowerShell): what is listening
Get-NetTCPConnection -LocalPort 5601 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}From another machine: is it reachable
nc -zv HOST 5601
# or
nmap -p 5601 HOST
# Windows
Test-NetConnection HOST -Port 5601Test the Kibana service itself
curl -sI http://HOST:5601/api/statusRestrict port 5601 in the firewall
Replace 10.0.0.0/8 with the network or address that needs access. Docker publishes container ports through its own iptables rules, which bypass ufw; bind published ports to 127.0.0.1 (-p 127.0.0.1:5601:5601) instead of relying on the host firewall.
ufw: allow only your private network, deny everyone else
sudo ufw allow from 10.0.0.0/8 to any port 5601 proto tcp
sudo ufw deny 5601/tcpfirewalld: allow one source network only
sudo firewall-cmd --permanent --remove-port=5601/tcp
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="5601" protocol="tcp" accept'
sudo firewall-cmd --reloadiptables
sudo iptables -A INPUT -p tcp --dport 5601 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 5601 -j DROPWindows Firewall (PowerShell, as Administrator)
New-NetFirewallRule -DisplayName "Block 5601 from internet" -Direction Inbound -Protocol TCP -LocalPort 5601 -RemoteAddress Internet -Action BlockMonitor port 5601
Run a TCP port monitor against your public IP on port 5601: here, a failed connection is the healthy result, so you know the firewall is still doing its job. On Linux, the Statance agent also reports every listening port on the server. TCP port monitoring.
Related ports
| Port 9200 | Elasticsearch (HTTP API) | Critical risk |
| Port 9300 | Elasticsearch (transport) | High risk |
| Port 3000 | Grafana / Node.js development servers | Medium risk |
FAQ
What is port 5601 used for?
Port 5601 is Kibana (and OpenSearch Dashboards), the web interface for searching and visualising Elasticsearch data. It is also used by Kibana, OpenSearch Dashboards.
Is it safe to open port 5601?
Not to the public internet. Kibana shows whatever is in Elasticsearch, often application logs with personal data, tokens and internal hostnames. Without security enabled on the cluster, it has no login at all. Older Kibana releases have also had remote code execution flaws.
Is port 5601 TCP or UDP?
Kibana uses TCP on port 5601.
How do I check if port 5601 is open?
On the server, run sudo ss -tulpn | grep ':5601 ' (Linux) or Get-NetTCPConnection -LocalPort 5601 (Windows) to see what is listening. From another machine, run nc -zv HOST 5601 or Test-NetConnection HOST -Port 5601.
Know the moment a port stops answering.
TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.