Is port 5432 (PostgreSQL) safe to expose?
PostgreSQL database. Exposing it to the internet is high risk.
Why exposing port 5432 is risky
Like any database, exposing it to the internet invites brute-forcing and exploitation; it belongs on a private network.
How to check if it's exposed
From outside your network, a quick nmap -p 5432 <your-ip> (or an external port scanner) shows whether 5432 answers. On the host, ss -tlnp | grep :5432 shows what's listening and on which interface — it should be a private address, not 0.0.0.0.
How to secure it
- Set listen_addresses to private interfaces and tighten pg_hba.conf.
- Restrict the firewall to the app servers that need it.
SkyShield watches what's really exposed
SkyShield follows your firewall rules through to the container and shows what the internet can actually reach. Free for one server, then from $49 per server a month. Start free.