Port 6432PgBouncer
PgBouncer is a lightweight connection pooler designed to optimize PostgreSQL database connections, improving performance and resource management. Acting as an intermediary between client applications and the database server, it maintains a pool of established connections to reduce the overhead of repeatedly opening and closing database connections. This efficiency makes PgBouncer particularly useful in high-traffic environments, reducing latency and enhancing scalability..
- transport
- tcp
- in transit
- cleartext
- assignment
- official
- risk
- 4/10
- lookups
- 8,714
single transport
payload readable on path
registered with iana
caution
rank 581 of 993 · top 58%
Technical Details
what runs on :6432PgBouncer is an open-source connection pooler specifically built for PostgreSQL databases. Its primary purpose is to maintain and manage a pool of persistent database connections, allowing client applications to reuse these connections rather than creating a new one each time. This greatly reduces the connection overhead and aids in resource optimization.
It supports multiple pooling modes such as session pooling, transaction pooling, and statement pooling, catering to various application requirements. Session pooling assigns a connection for the entire duration of a client session, while transaction pooling maintains a connection only during transactions, and statement pooling releases the connection after each individual statement.
Typically running as a separate lightweight service, PgBouncer listens on the default port 6432 by convention. It supports authentication methods compatible with PostgreSQL and can be configured for logging, connection limits, idle timeouts, and SSL encryption (although not enabled by default). Its simplicity and minimal resource consumption make it a popular choice for scaling PostgreSQL deployments.
Security Information
exposure of :6432risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
databases averages 4.0 across 58 ports — this one sits level with it.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
official
registered with iana for this service — scanners fingerprint it by number
reachable over
tcp
every listening transport is another surface to filter at the edge
security overview
Common Vulnerabilities:
- Improper configuration can expose PgBouncer to unauthorized access and potential data breaches.
- Lack of encryption on connections can enable eavesdropping and Man-in-the-Middle (MitM) attacks.
- Weak or default authentication credentials can be exploited by attackers.
- If used with statement pooling, sensitive information leaks are possible if cleanup is improperly handled.
Common Mitigations:
- Enforce strong authentication using PostgreSQL-compatible methods, including SCRAM-SHA-256.
- Enable SSL/TLS encryption on both client-to-PgBouncer and PgBouncer-to-PostgreSQL connections to secure data in transit.
- Limit access to trusted hosts via firewalls, network segmentation, and PgBouncer's own access control features.
- Regularly update PgBouncer to patch vulnerabilities.
- Audit configurations and apply the principle of least privilege to user accounts connecting through PgBouncer.
Related Ports
the 8 most looked-up other ports in databases — 58 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :8882 | Atlasz Secure App Server | TCP | Web Services | caution | 66.9k |
| :9001 | ETL Service Manager | TCPUDP | Databases | caution | 28.6k |
| :2484 | Oracle SSL Listener | TCPUDPtls | Security | caution | 25.0k |
| :5495 | Applix TM1 Admin | TCP | Databases | caution | 24.8k |
| :591 | FileMaker Web Sharing | TCP | Web Services | caution | 23.1k |
| :1521 | Oracle TNS Listener | TCP | Security | caution | 19.6k |
| :21001 | AMLFilter Admin | TCP | Security | caution | 19.2k |
| :18206 | Audition FAM DB | TCPUDP | Databases | caution | 19.1k |
risk mix of the 8 listed
- caution100%
1 of 8 encrypted