How to Check If a Port Is Open (Without a Terminal)

You configured the firewall rule. You restarted the service. The application still cannot connect. Before you spend an hour reading logs, check the obvious thing first — is the port actually reachable from outside the machine? That single check eliminates or confirms the firewall as the problem in seconds.

This post is specifically about checking whether a port is open or closed. For a reference on what each port number is used for, see The Ports Every Sysadmin Should Know.

What open, closed, and filtered mean

When you test a port, you get one of three results:

Open — something is actively listening on that port and accepted the connection. The service is running and reachable.

Closed — the port is reachable but nothing is listening. The host responded with a reset. This usually means the service is not running, not that a firewall is blocking it.

Filtered — no response came back. The connection timed out. This typically means a firewall is silently dropping packets to that port. You cannot distinguish between "port is blocked" and "host is unreachable" from this result alone.

Understanding the difference matters. Closed means the service is down. Filtered means something between you and the server is blocking it. They require different fixes.

How to check in the browser

Go to the ToolsKit Port Checker tool. Enter the IP address or hostname and the port number you want to test. Click Check Port. The result tells you immediately whether the port is open, closed, or filtered.

No nmap. No telnet. No terminal session required. Works from any device, including your phone.

How to check from the terminal

If you do have terminal access, these are the standard methods.

Using telnet (simple, available on most systems):

telnet hostname port

If the connection opens, the port is open. If it immediately closes or times out, it is not.

Using nmap (more detail, requires installation):

nmap -p port hostname

Using PowerShell on Windows:

Test-NetConnection -ComputerName hostname -Port port

Using curl (for HTTP/HTTPS ports specifically):

curl -v telnet://hostname:port

The browser tool is faster for quick checks. The terminal tools are better when you need to test from a specific machine or script the check.

Common scenarios where this saves time

Web server not responding. Test port 80 and 443. If both show filtered, the issue is the firewall, not the web server itself.

SSH connection refused. Test port 22. Closed means the SSH daemon is not running. Filtered means a firewall or security group is blocking it.

Database connection failing from an application. Test port 3306 (MySQL) or 5432 (PostgreSQL). These ports are almost always blocked by default on cloud providers and need to be explicitly opened.

Remote desktop not connecting. Test port 3389. Filtered is the most common result — Windows Firewall blocks it unless RDP is enabled in the settings.

Why your port might show closed even when the service is running

There are a few reasons this happens.

The service is bound to localhost only. A service listening on 127.0.0.1:8080 is not reachable externally, even if it is running. It needs to bind to 0.0.0.0 or the specific external interface to be reachable.

The firewall is allowing the port but NAT or port forwarding is not set up. Common in home labs and cloud environments.

The service crashed after starting. It was running when you configured the firewall, but it is not running now.

You are checking the wrong IP. If the server has multiple interfaces, confirm you are testing the public-facing one.

Frequently Asked Questions

Why does the port checker show closed even when my service is running?

The most common cause is a firewall — either on the host OS, the cloud provider security group, or a network device — blocking inbound connections before they reach the service.

What is the difference between open, closed, and filtered?

Open means the port accepted the connection. Closed means the host responded but nothing is listening. Filtered means no response — typically a firewall is silently dropping packets.

Can I test a port on my own machine?

The online tool tests connectivity from the internet to your host, so it only works for publicly accessible IPs. For local testing, use telnet, nc (netcat), or nmap from the terminal.