Port 9100 is used by Prometheus node_exporter to publish host metrics, and separately by network printers for raw print jobs (JetDirect/AppSocket). It should not be reachable from the public internet.
- Port
- 9100
- Protocol
- TCP
- Service
- Prometheus node_exporter / JetDirect printing
- Expose to internet?
- No
- Also used by
- node_exporter, HP JetDirect / raw printing (AppSocket)
Is port 9100 safe to open?
An exposed node_exporter reveals detailed system information: kernel version, filesystems, network interfaces and running services, useful for planning an attack. An exposed printer port accepts jobs from anyone and has been abused to print spam to thousands of printers.
How to secure Prometheus node_exporter / JetDirect printing
- Allow 9100 only from your Prometheus server.
- Enable TLS and basic auth on node_exporter with
--web.config.file. - Never forward printer ports from the internet.
Check if port 9100 is open
Linux: what is listening on this port
sudo ss -tlpn | grep ':9100 'Windows (PowerShell): what is listening
Get-NetTCPConnection -LocalPort 9100 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}From another machine: is it reachable
nc -zv HOST 9100
# or
nmap -p 9100 HOST
# Windows
Test-NetConnection HOST -Port 9100Test the Prometheus node_exporter / JetDirect printing service itself
curl -s http://HOST:9100/metrics | headRestrict port 9100 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:9100:9100) 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 9100 proto tcp
sudo ufw deny 9100/tcpfirewalld: allow one source network only
sudo firewall-cmd --permanent --remove-port=9100/tcp
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="9100" protocol="tcp" accept'
sudo firewall-cmd --reloadiptables
sudo iptables -A INPUT -p tcp --dport 9100 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 9100 -j DROPWindows Firewall (PowerShell, as Administrator)
New-NetFirewallRule -DisplayName "Block 9100 from internet" -Direction Inbound -Protocol TCP -LocalPort 9100 -RemoteAddress Internet -Action BlockMonitor port 9100
Run a TCP port monitor against your public IP on port 9100: 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 631 | IPP (CUPS printing) | High risk |
| Port 19999 | Netdata dashboard | Medium risk |
FAQ
What is port 9100 used for?
Port 9100 is used by Prometheus node_exporter to publish host metrics, and separately by network printers for raw print jobs (JetDirect/AppSocket). It is also used by node_exporter, HP JetDirect / raw printing (AppSocket).
Is it safe to open port 9100?
Not to the public internet. An exposed node_exporter reveals detailed system information: kernel version, filesystems, network interfaces and running services, useful for planning an attack. An exposed printer port accepts jobs from anyone and has been abused to print spam to thousands of printers.
Is port 9100 TCP or UDP?
Prometheus node_exporter / JetDirect printing uses TCP on port 9100.
How do I check if port 9100 is open?
On the server, run sudo ss -tulpn | grep ':9100 ' (Linux) or Get-NetTCPConnection -LocalPort 9100 (Windows) to see what is listening. From another machine, run nc -zv HOST 9100 or Test-NetConnection HOST -Port 9100.
Know the moment a port stops answering.
TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.