Port 8086 is the InfluxDB HTTP API, used to write and query time-series data such as metrics from Telegraf. It should not be reachable from the public internet.
- Port
- 8086
- Protocol
- TCP
- Service
- InfluxDB
- Expose to internet?
- No
Is port 8086 safe to open?
InfluxDB 1.x has authentication turned off unless auth-enabled = true is set, so exposed instances can be read and wiped by anyone. InfluxDB 2.x requires tokens, but leaked tokens in dashboards or scripts are common. Metrics often reveal hostnames, internal IPs and business data.
How to secure InfluxDB
- On 1.x, set
auth-enabled = truein the [http] section and create an admin user. - On 2.x, give each writer a token scoped to a single bucket.
- Bind to localhost or a private address and enable HTTPS.
Check if port 8086 is open
Linux: what is listening on this port
sudo ss -tlpn | grep ':8086 'Windows (PowerShell): what is listening
Get-NetTCPConnection -LocalPort 8086 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}From another machine: is it reachable
nc -zv HOST 8086
# or
nmap -p 8086 HOST
# Windows
Test-NetConnection HOST -Port 8086Test the InfluxDB service itself
curl -s http://HOST:8086/ping -iRestrict port 8086 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:8086:8086) 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 8086 proto tcp
sudo ufw deny 8086/tcpfirewalld: allow one source network only
sudo firewall-cmd --permanent --remove-port=8086/tcp
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="8086" protocol="tcp" accept'
sudo firewall-cmd --reloadiptables
sudo iptables -A INPUT -p tcp --dport 8086 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 8086 -j DROPWindows Firewall (PowerShell, as Administrator)
New-NetFirewallRule -DisplayName "Block 8086 from internet" -Direction Inbound -Protocol TCP -LocalPort 8086 -RemoteAddress Internet -Action BlockMonitor port 8086
Run a TCP port monitor against your public IP on port 8086: 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 9090 | Prometheus / Cockpit | Medium risk |
| Port 3000 | Grafana / Node.js development servers | Medium risk |
| Port 9100 | Prometheus node_exporter / JetDirect printing | Medium risk |
FAQ
What is port 8086 used for?
Port 8086 is the InfluxDB HTTP API, used to write and query time-series data such as metrics from Telegraf.
Is it safe to open port 8086?
Not to the public internet. InfluxDB 1.x has authentication turned off unless auth-enabled = true is set, so exposed instances can be read and wiped by anyone. InfluxDB 2.x requires tokens, but leaked tokens in dashboards or scripts are common. Metrics often reveal hostnames, internal IPs and business data.
Is port 8086 TCP or UDP?
InfluxDB uses TCP on port 8086.
How do I check if port 8086 is open?
On the server, run sudo ss -tulpn | grep ':8086 ' (Linux) or Get-NetTCPConnection -LocalPort 8086 (Windows) to see what is listening. From another machine, run nc -zv HOST 8086 or Test-NetConnection HOST -Port 8086.
Know the moment a port stops answering.
TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.