TCP 9092
Synopsis
- Apache Kafka brokers (including Confluent Platform) commonly listen on TCP 9092 for the Kafka client/broker endpoint (PLAINTEXT or SASL_PLAINTEXT).
- Kafka-compatible platforms like Redpanda also default to 9092 for the Kafka API.
- Kubernetes deployments—such as Strimzi Kafka Operator and the Bitnami Kafka Helm chart—expose broker listeners on 9092 by default.
- Managed Kafka services (e.g., Confluent Cloud and AWS MSK) often provide a 9092 listener; TLS variants are frequently on 9093 or 9094 depending on provider/config.
- The H2 Database Engine’s TCP server uses 9092 by default for database connections (jdbc:h2:tcp://host:9092/...).
- Popular Docker images (bitnami/kafka, wurstmeister/kafka) and docker-compose examples map brokers to 9092 out of the box.
- Security note: exposed 9092 Kafka endpoints have been abused by attackers to consume/produce data, create/delete topics, or pivot inside networks when authN/authZ is disabled or misconfigured.
Observed activity
Last 30 days
Detailed chart