Security & SEO

    Exposed Services & Port Scanning

    Identify open ports and exposed services on your server.

    Updated 2026-03-16
    2 min read
    ports
    exposed services
    security

    Exposed Services & Port Scanning#

    LemWatch checks which services and ports are visible on your server's IP address, helping you identify potential security risks.

    What Gets Checked#

  1. Open ports — Which TCP ports are accepting connections (80, 443, 22, 3306, etc.)
  2. Running services — What software is responding on each port (Apache, Nginx, MySQL, SSH)
  3. Service versions — Detected software versions (which may have known vulnerabilities)
  4. Known vulnerabilities — CVEs associated with detected service versions
  5. Risk assessment — Overall risk level based on exposed services
  6. Risk Levels#

    LevelDescription
    LowOnly expected ports open (80, 443)
    MediumAdmin ports open (22/SSH) but properly configured
    HighDatabase ports exposed (3306, 5432) or outdated services
    CriticalKnown vulnerabilities in exposed services

    Common Issues#

  7. Database ports open — MySQL (3306), PostgreSQL (5432), MongoDB (27017) should never be publicly accessible
  8. FTP port open — Port 21 is insecure; use SFTP (port 22) instead
  9. Admin panels exposed — phpMyAdmin, cPanel, or custom admin on public ports
  10. Outdated software — Running old versions of Apache, Nginx, or OpenSSH with known CVEs
  11. How to Fix#

  12. Close unnecessary ports — Use firewall rules (iptables, ufw, or cloud security groups)
  13. Update software — Patch services to the latest versions
  14. Use VPN for admin access — Don't expose SSH, databases, or admin panels publicly
  15. Move databases behind a firewall — Database servers should only accept connections from your application servers
  16. Was this article helpful?