Port check explained

What open, closed and timed out mean

An open port usually means a service accepted the connection. A closed port means the host responded but no service accepted the connection. A timeout often means a firewall, routing rule or provider policy dropped the traffic. Results can vary depending on where the check is performed from.

Common examples include 80 for HTTP, 443 for HTTPS, 22 for SSH, 25 for SMTP, 587 for mail submission and 3306 for MySQL. Public exposure should be intentional, especially for admin, database and control panel ports.

When to use a port checker

Use port checks after changing firewall rules, launching a web server, configuring a reverse proxy, opening a game server, debugging email delivery, or confirming that a hosting provider allows inbound traffic. A port can be open from one network and blocked from another, so external testing is valuable.

Port troubleshooting checklist

First confirm that the service is actually running on the server. Then check the local firewall, cloud firewall, hosting security group, router port forwarding and provider restrictions. If the service listens only on 127.0.0.1, it may work locally but remain closed from the public internet. If the service listens on the wrong interface or protocol, an external checker may time out.

For websites, test both 80 and 443. For mail, check whether the provider blocks outbound or inbound SMTP ports. For databases and admin panels, avoid exposing ports publicly unless there is a clear security plan.

FAQ

Does an open port mean the service is safe? No. It only means a connection was accepted. Security depends on authentication, patching, configuration and access control.

Why does a port time out? A timeout often means traffic was dropped by a firewall, router, provider or network path.

Can a CDN affect port results? Yes. If a domain points to a CDN, the port check may test the CDN edge rather than your origin server.

Common port examples

Websites: ports 80 and 443 are the normal HTTP and HTTPS ports. If 443 is closed, browsers cannot establish a normal HTTPS session. If 80 is closed but 443 is open, the website may still work, but HTTP-to-HTTPS redirects from old links may fail.

Remote access: SSH commonly uses port 22, but many administrators move SSH to a custom port to reduce noise from automated scans. A custom SSH port should still be protected by keys, firewall rules and login hardening.

Email: mail systems may use ports 25, 465, 587, 993 and 995. Hosting providers often restrict port 25 to reduce spam, so email troubleshooting should include provider policy checks.

Databases: database ports should rarely be exposed publicly. If MySQL, PostgreSQL, Redis or similar services appear open to the internet, review firewall rules and bind addresses immediately.