bitlvl
EN

Port 9092 Kafka · TCP

Apache Kafka broker port (PLAINTEXT listener). Kafka's "advertised.listeners" is the setting behind most connection problems: the broker tells clients which address to use for the follow-up connections, and if that is an internal hostname, external clients get the first connection and then time out.

Port9092
TransportTCP
ServiceKafka
CategoryMessage queues
Rangeregistered (1024–49151)
EncryptedOptional, must be configured
ExposurePrivate network or VPN only

What runs on port 9092

Apache Kafka broker port (PLAINTEXT listener). Kafka's "advertised.listeners" is the setting behind most connection problems: the broker tells clients which address to use for the follow-up connections, and if that is an internal hostname, external clients get the first connection and then time out. 9093 is the usual TLS listener; KRaft controllers use 9093 or 9094 too.

Software that uses it: Apache Kafka · Confluent Platform · Redpanda (same port) · Amazon MSK, Aiven, Confluent Cloud

Should port 9092 be open?

Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.

Check port 9092

# on the host: is anything listening, and which process?
ss -ltnp 'sport = :9092'
sudo lsof -i :9092

# from another machine: is it reachable?
nc -zv host 9092
nmap -p 9092 host
curl -v telnet://host:9092      # raw TCP connect test, Ctrl-C to leave

A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.

Allow or block port 9092

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 9092 proto tcp
sudo ufw deny 9092/tcp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 9092 accept
nft add rule inet filter input tcp dport 9092 drop

# iptables (legacy)
iptables -A INPUT -p tcp --dport 9092 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 9092 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=9092 protocol=tcp accept'

Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 9092" with no source is just "open".

Related ports

Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.

Questions

Is port 9092 TCP or UDP?

TCP. Kafka is a connection-oriented protocol; there is no UDP service on 9092 by default (a scanner reporting UDP 9092 open is usually seeing a filtered port).

Is port 9092 encrypted?

Optional, must be configured. Turn encryption on in the service configuration before using it across any network you do not control.

How do I check whether port 9092 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 9092 and which process. From another machine, nc -zv host 9092 or nmap -p 9092 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can Kafka run on a different port?

Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.