Common Port Numbers Reference
Search any port number or service · see what normally runs there and whether it belongs on the public internet.
100% client-side · nothing you enter is ever sent to a server or stored.
Preview · sign in with a free account to run it
75 of 75 ports
Data channel for active-mode FTP.
Safer alternative: SFTP over SSH (22)
File transfer control channel · credentials travel in cleartext · prefer SFTP (22).
Safer alternative: SFTP over SSH (22)
Secure shell and file transfer · a top brute-force target · use keys, disable passwords.
Safer alternative: SSH / SFTP behind a VPN or a firewall allowlist with authenticated encrypted access
Unencrypted remote shell · everything including passwords is visible on the wire.
Safer alternative: SSH (22)
Server-to-server mail delivery · commonly public for MTAs · block outbound 25 on non-mail hosts.
Safer alternative: Authenticated mail submission with STARTTLS (587)
Name resolution · public for authoritative servers · never run an open recursive resolver.
Safer alternative: DNS with current TLS, authentication where supported, and a patched, narrowly configured listener
Hands out IP addresses on the local network only.
Safer alternative: DHCP server on a private network through a VPN or SSH tunnel; require authentication and TLS
Trivial file transfer · no auth at all · legacy netboot only.
Safer alternative: TFTP on a private network through a VPN or SSH tunnel; require authentication and TLS
Plain web traffic · keep it open mainly to redirect to HTTPS.
Safer alternative: HTTPS (443)
Active Directory authentication · internal identity infrastructure.
Safer alternative: Kerberos on a private network through a VPN or SSH tunnel; require authentication and TLS
Legacy mail retrieval · unencrypted · prefer POP3S (995).
Safer alternative: POP3 over TLS (995)
Maps RPC services (NFS etc.) · classic recon and amplification target.
Safer alternative: rpcbind / portmapper on a private network through a VPN or SSH tunnel; require authentication and TLS
Time sync · misconfigured servers fuel amplification DDoS attacks.
Safer alternative: NTP behind a VPN or a firewall allowlist with authenticated encrypted access
Windows RPC endpoint mapper · repeatedly exploited · LAN only.
Safer alternative: MS RPC on a private network through a VPN or SSH tunnel; require authentication and TLS
Legacy Windows name resolution · leaks host info.
Safer alternative: NetBIOS name on a private network through a VPN or SSH tunnel; require authentication and TLS
Legacy SMB over NetBIOS · LAN only.
Safer alternative: NetBIOS session on a private network through a VPN or SSH tunnel; require authentication and TLS
Mail retrieval · unencrypted · prefer IMAPS (993).
Safer alternative: IMAP over TLS (993)
Device monitoring · v1/v2 “community strings” are basically passwords in cleartext.
Safer alternative: SNMPv3 on a private management network
Internet routing between peers · only open to configured neighbors.
Safer alternative: BGP behind a VPN or a firewall allowlist with authenticated encrypted access
Directory services · exposed LDAP leaks your whole org tree · CLDAP amplifies DDoS.
Safer alternative: LDAP over TLS (636)
TLS web traffic · the port your app should live on.
Safer alternative: HTTPS with current TLS, authentication where supported, and a patched, narrowly configured listener
Windows file sharing · WannaCry/EternalBlue territory · never internet-facing.
Safer alternative: SMB3 over an owner-controlled VPN
Mail submission over implicit TLS · public on mail servers.
Safer alternative: SMTPS with current TLS, authentication where supported, and a patched, narrowly configured listener
VPN key exchange · public only when this host is a VPN endpoint.
Safer alternative: IKE (IPsec) with current TLS, authentication where supported, and a patched, narrowly configured listener
Log shipping · unauthenticated · attackers can flood or forge logs.
Safer alternative: Syslog on a private network through a VPN or SSH tunnel; require authentication and TLS
Authenticated mail submission with STARTTLS · public on mail servers.
Safer alternative: SMTP submission with current TLS, authentication where supported, and a patched, narrowly configured listener
Printing · recent CUPS RCEs · local network only.
Safer alternative: IPP / CUPS on a private network through a VPN or SSH tunnel; require authentication and TLS
LDAP over TLS · encrypted but still internal directory infrastructure.
Safer alternative: LDAPS on a private network through a VPN or SSH tunnel; require authentication and TLS
Encrypted DNS · public if you operate a DoT resolver.
Safer alternative: DNS over TLS with current TLS, authentication where supported, and a patched, narrowly configured listener
File sync daemon · anonymous modules leak data constantly in the wild.
Safer alternative: rsync on a private network through a VPN or SSH tunnel; require authentication and TLS
IMAP over TLS · the standard way clients read mail · public on mail servers.
Safer alternative: IMAPS with current TLS, authentication where supported, and a patched, narrowly configured listener
POP3 over TLS · public on mail servers.
Safer alternative: POP3S with current TLS, authentication where supported, and a patched, narrowly configured listener
Open SOCKS proxies get abused for attack relay within hours.
Safer alternative: SOCKS proxy on a private network through a VPN or SSH tunnel; require authentication and TLS
VPN tunnel · public only when this host is a VPN endpoint.
Safer alternative: OpenVPN with current TLS, authentication where supported, and a patched, narrowly configured listener
Database · constant brute-force scanning · private network only.
Safer alternative: Microsoft SQL Server on a private network through a VPN or SSH tunnel; require authentication and TLS
Database listener · private network only.
Safer alternative: Oracle DB on a private network through a VPN or SSH tunnel; require authentication and TLS
Obsolete VPN protocol with broken crypto · replace with WireGuard/OpenVPN.
Safer alternative: WireGuard or IKEv2 VPN
Network file system · exposed shares mean exposed files.
Safer alternative: NFS on a private network through a VPN or SSH tunnel; require authentication and TLS
Cluster coordination · no auth by default · controls Kafka/Hadoop state.
Safer alternative: ZooKeeper on a private network through a VPN or SSH tunnel; require authentication and TLS
Unauthenticated remote root · exposed daemons are cryptojacked within minutes.
Safer alternative: Docker API (no TLS) on a private network through a VPN or SSH tunnel; require authentication and TLS
Remote Docker with client certs · still safer over VPN.
Safer alternative: Docker API (TLS) behind a VPN or a firewall allowlist with authenticated encrypted access
Default for many dev tools · dev servers must not face the internet · bind to 127.0.0.1 and tunnel if you need remote access.
Safer alternative: Dev server · Node/Rails/Grafana behind a VPN or a firewall allowlist with authenticated encrypted access
Open proxies get abused for anonymous attacks and fraud.
Safer alternative: Squid proxy on a private network through a VPN or SSH tunnel; require authentication and TLS
Database · one of the most-scanned ports on the internet.
Safer alternative: MySQL / MariaDB on a private network through a VPN or SSH tunnel; require authentication and TLS
Windows remote desktop · ransomware's favorite front door · VPN or gateway only.
Safer alternative: RDP through a VPN or authenticated Remote Desktop Gateway
Angular CLI default · dev servers must not face the internet · bind to 127.0.0.1 and tunnel if you need remote access.
Safer alternative: Dev server · Angular behind a VPN or a firewall allowlist with authenticated encrypted access
IPsec through NAT · public only on VPN endpoints.
Safer alternative: IPsec NAT-T with current TLS, authentication where supported, and a patched, narrowly configured listener
Flask default (and macOS AirPlay) · dev servers must not face the internet · bind to 127.0.0.1 and tunnel if you need remote access.
Safer alternative: Dev server · Flask / AirPlay behind a VPN or a firewall allowlist with authenticated encrypted access
VoIP signaling · exposed PBXes get toll-fraud attacks daily.
Safer alternative: SIP behind a VPN or a firewall allowlist with authenticated encrypted access
Vite default · dev servers must not face the internet · bind to 127.0.0.1 and tunnel if you need remote access.
Safer alternative: Dev server · Vite behind a VPN or a firewall allowlist with authenticated encrypted access
Local service discovery (Bonjour) · leaks device info · LAN only by design.
Safer alternative: mDNS on a private network through a VPN or SSH tunnel; require authentication and TLS
Database · use a private network or SSL-enforced allowlist, never 0.0.0.0.
Safer alternative: PostgreSQL on a private network through a VPN or SSH tunnel; require authentication and TLS
Elasticsearch dashboard · exposed instances leak whole log histories.
Safer alternative: Kibana on a private network through a VPN or SSH tunnel; require authentication and TLS
Message broker · internal plumbing, never public.
Safer alternative: RabbitMQ (AMQP) on a private network through a VPN or SSH tunnel; require authentication and TLS
Remote desktop · often password-less or weakly protected · a top compromise vector.
Safer alternative: VNC on a private network through a VPN or SSH tunnel; require authentication and TLS
Database with HTTP API · historically ransomed en masse when exposed.
Safer alternative: CouchDB on a private network through a VPN or SSH tunnel; require authentication and TLS
Windows remote management · lateral-movement highway · internal only.
Safer alternative: WinRM on a private network through a VPN or SSH tunnel; require authentication and TLS
In-memory store · no auth by default · exposed instances are owned in minutes.
Safer alternative: Redis on a private network through a VPN or SSH tunnel; require authentication and TLS
Cluster control plane · restrict to admin IPs or private network.
Safer alternative: Kubernetes API behind a VPN or a firewall allowlist with authenticated encrypted access
Django/uvicorn default · dev servers must not face the internet · bind to 127.0.0.1 and tunnel if you need remote access.
Safer alternative: Dev server · Django behind a VPN or a firewall allowlist with authenticated encrypted access
HDFS metadata service · exposed clusters get wiped and ransomed.
Safer alternative: Hadoop NameNode RPC on a private network through a VPN or SSH tunnel; require authentication and TLS
Proxies, Tomcat, dev servers · if it's a real app, put it behind a reverse proxy on 443.
Safer alternative: HTTP alternate behind a VPN or a firewall allowlist with authenticated encrypted access
Admin consoles often live here · restrict to known IPs.
Safer alternative: HTTPS alternate behind a VPN or a firewall allowlist with authenticated encrypted access
Executes arbitrary code by design · token auth or nothing · never public.
Safer alternative: Jupyter Notebook on a private network through a VPN or SSH tunnel; require authentication and TLS
Exposed PHP-FPM allows code execution · keep behind the web server.
Safer alternative: PHP-FPM / SonarQube / MinIO on a private network through a VPN or SSH tunnel; require authentication and TLS
Metrics server · no auth built in · leaks infrastructure internals.
Safer alternative: Prometheus on a private network through a VPN or SSH tunnel; require authentication and TLS
Event streaming broker · internal data plumbing only.
Safer alternative: Kafka on a private network through a VPN or SSH tunnel; require authentication and TLS
Search/analytics API · no auth by default in older versions · infamous for data leaks.
Safer alternative: Elasticsearch on a private network through a VPN or SSH tunnel; require authentication and TLS
HDFS web UI · browse-and-delete access to your data lake.
Safer alternative: Hadoop NameNode UI on a private network through a VPN or SSH tunnel; require authentication and TLS
Per-node Kubernetes agent · exec-into-container access if exposed.
Safer alternative: kubelet API on a private network through a VPN or SSH tunnel; require authentication and TLS
Cache · no auth · UDP mode powered record-breaking DDoS amplification.
Safer alternative: Memcached on a private network through a VPN or SSH tunnel; require authentication and TLS
Broker admin UI · default guest/guest credentials · internal only.
Safer alternative: RabbitMQ management on a private network through a VPN or SSH tunnel; require authentication and TLS
Database · tens of thousands of exposed instances have been ransomed.
Safer alternative: MongoDB on a private network through a VPN or SSH tunnel; require authentication and TLS
Media streaming · keep patched and prefer relay/VPN over direct exposure.
Safer alternative: Plex Media Server behind a VPN or a firewall allowlist with authenticated encrypted access
Modern VPN · public only when this host is a VPN endpoint · silent to scanners.
Safer alternative: WireGuard with current TLS, authentication where supported, and a patched, narrowly configured listener
How to use it
- Search by port number or service name, such as 5432 or ssh.
- Read what runs there, and whether it's fine to expose, should be restricted, or should never face the internet.
- Follow the safer alternative for anything in the never-expose group.
Example
Input
5432
Result
5432/TCP PostgreSQL Database · use a private network or SSL-enforced allowlist, never 0.0.0.0. Exposure: should never face the internet
The three exposure levels
- Fine to expose
- Services meant to be public, such as 443 for HTTPS. Keep them patched and use TLS.
- Expose only if required
- Such as 22 (SSH). Lock it down with firewall allowlists, VPN, key-only sign-in and rate limiting.
- Should never face the internet
- Databases (5432, 3306, 27017), Redis (6379), Elasticsearch and admin dashboards. Bind them to localhost or a private network.
Go deeper
Page updated
Frequently asked questions
Which ports should never be publicly exposed?
Databases (5432 Postgres, 3306 MySQL, 27017 MongoDB, 6379 Redis), remote admin (3389 RDP, 23 Telnet), and file shares (445 SMB). Shodan indexes them within hours of exposure · put them behind a VPN or private network.
Is running SSH on a non-standard port real security?
It cuts log noise from automated scans, nothing more · scanners find it anyway. Real SSH hardening is key-only auth, no root login, and fail2ban or a VPN. Obscurity is seasoning, not a meal.
Is moving SSH to another port real security?
It cuts log noise from automated scans, but anyone scanning all ports finds it. Use key-only sign-in and an allowlist for real protection.
Want the full picture?
This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.
Run a full security scanRelated tools
Regex Tester
Write a pattern, paste test text, and see matches highlighted live · with capture groups, flags, and match positions.
Cron Parser
Paste any cron expression and get a plain-English schedule plus the next five run times · no more guessing what */15 2,14 * * 1-5 means.
Semver Checker
Enter a version range like ^4.2.0 and a version to test · see whether it matches and what the range actually allows.