๐Ÿ”Œ

Common Ports Reference

Look up what runs on a TCP or UDP port and whether it belongs on the public internet

Why this isn't a live scanner: scanning someone else's server from our infrastructure would be a network-abuse problem, not a privacy-friendly browser tool โ€” and it is something you should run yourself, against hosts you own. To test your own ports, use nmap -Pn yourhost or nc -vz yourhost 443 from your machine. This reference explains what you find.
32 of 32 ports
  • 20
    FTP (data)TCPKeep internal

    File Transfer Protocol data channel. Unencrypted.

  • 21
    FTP (control)TCPKeep internal

    File Transfer Protocol commands. Credentials travel in clear text โ€” prefer SFTP on 22.

  • 22
    SSH / SFTPTCPExpose with care

    Encrypted remote shell and file transfer. Use key auth and disable password login.

  • 23
    TelnetTCPKeep internal

    Unencrypted remote shell. Obsolete โ€” should never be exposed to the internet.

  • 25
    SMTPTCPExpose with care

    Mail transfer between servers. Often blocked by hosting providers to limit spam.

  • 53
    DNSTCP/UDPExpose with care

    Domain name resolution. An open recursive resolver can be abused for amplification attacks.

  • 67
    DHCP (server)UDPKeep internal

    Assigns IP addresses on a local network. Should never be reachable from the internet.

  • 80
    HTTPTCPSafe to expose

    Unencrypted web traffic. Normally redirected to HTTPS on 443.

  • 110
    POP3TCPExpose with care

    Mail retrieval, deletes from server by default. Superseded by IMAP over TLS (993).

  • 123
    NTPUDPExpose with care

    Time synchronisation. Misconfigured servers are used in amplification attacks.

  • 143
    IMAPTCPExpose with care

    Mail access without encryption. Use 993 (IMAPS) instead.

  • 161
    SNMPUDPKeep internal

    Device monitoring. Default community strings ("public") leak system detail.

  • 389
    LDAPTCPKeep internal

    Directory services, unencrypted. Use LDAPS on 636.

  • 443
    HTTPSTCPSafe to expose

    Encrypted web traffic. The default for any modern site.

  • 445
    SMBTCPKeep internal

    Windows file sharing. A frequent ransomware entry point โ€” never expose publicly.

  • 465
    SMTPSTCPSafe to expose

    Mail submission over implicit TLS.

  • 587
    SMTP (submission)TCPSafe to expose

    The standard port for mail clients sending via STARTTLS.

  • 993
    IMAPSTCPSafe to expose

    IMAP over TLS โ€” the recommended way to read mail.

  • 995
    POP3STCPSafe to expose

    POP3 over TLS.

  • 1433
    MS SQL ServerTCPKeep internal

    Microsoft SQL Server. Bind to localhost or a private network only.

  • 1521
    Oracle DBTCPKeep internal

    Oracle database listener. Should not face the internet.

  • 3000
    Dev serverTCPSafe to expose

    Common default for Node, Next.js and Rails development servers.

  • 3306
    MySQL / MariaDBTCPKeep internal

    Database port. Exposing it publicly invites brute-force attempts.

  • 3389
    RDPTCPKeep internal

    Windows Remote Desktop. Put it behind a VPN โ€” it is heavily scanned.

  • 5432
    PostgreSQLTCPKeep internal

    Database port. Restrict with pg_hba.conf and a firewall.

  • 5900
    VNCTCPKeep internal

    Remote desktop. Weak default auth โ€” tunnel it over SSH.

  • 6379
    RedisTCPKeep internal

    In-memory store. Unauthenticated by default โ€” bind to localhost.

  • 8080
    HTTP alternateTCPExpose with care

    Proxies, app servers and admin panels. Often an unintentionally exposed backend.

  • 8443
    HTTPS alternateTCPExpose with care

    Secondary TLS port, common for admin interfaces.

  • 9200
    ElasticsearchTCPKeep internal

    Search cluster API. Historically exposed without auth, leaking whole datasets.

  • 11211
    MemcachedTCP/UDPKeep internal

    Cache server. UDP memcached enabled record-breaking amplification attacks.

  • 27017
    MongoDBTCPKeep internal

    Database port. Unauthenticated instances have been mass-ransomed.

Common Ports: What Runs Where

This reference explains what runs on each TCP and UDP port and whether it belongs on the public internet. Search by port number or service name to identify what you found in a scan, a firewall log, or a netstat listing.

Port scanning is essential for network administrators, security professionals, and system operators. It helps identify exposed services, verify that only necessary ports are accessible, and test firewall rules.

Understanding Port States

Open: A service is listening and accepting connections.
Closed: The port is accessible but no service is listening. Connection was refused.
Filtered: A firewall or filter is blocking access. No response was received within the timeout.

Common Ports & Services

Port 22 (SSH): Secure shell for remote server access.
Port 80 (HTTP): Standard unencrypted web traffic.
Port 443 (HTTPS): Encrypted web traffic (SSL/TLS).
Port 25 (SMTP): Email sending protocol.
Port 3306 (MySQL): MySQL database connections.
Port 3389 (RDP): Windows Remote Desktop.

Security Best Practices

โ€ข Close all unnecessary open ports
โ€ข Use a firewall to restrict access to essential services
โ€ข Keep all services updated with security patches
โ€ข Use fail2ban or similar to prevent brute force attacks
โ€ข Monitor port access logs for suspicious activity

FAQ

Is port scanning legal?

Port scanning your own systems is legal. Scanning third-party systems without permission may violate computer crime laws in many jurisdictions. Only scan hosts you own or have explicit permission to test.

Why are my ports showing as filtered?

Filtered ports indicate a firewall is dropping packets without response. This is often the default behavior for ports that are blockedโ€”more secure than actively refusing connections.