NetCheck Tools

Check If a Port Is Open

Enter a host and a port to instantly see if it accepts TCP connections from the internet — with clear guidance on what to do when it doesn't.

When a port that should be open isn't

Work through the chain from the inside out. Each step has a distinct failure signature, so the tool result tells you where to look:

  1. Is the service running? On the server: ss -tlnp (Linux) or netstat -ab (Windows). No listener → start or fix the service.
  2. Is it bound to the right interface? A listener on 127.0.0.1 only accepts local connections; it must bind 0.0.0.0 (or your public interface) for external access. Symptom from outside: timeout or closed.
  3. Does the OS firewall allow it? ufw status, firewall-cmd --list-all or Windows Firewall rules. Symptom: timeout.
  4. Does the network allow it? Cloud security groups, NAT/port-forwarding rules, corporate firewalls. Symptom: timeout.

Before all of this, confirm the hostname resolves to the server you think it does with a DNS lookup — testing the wrong IP is the classic wasted hour.

Frequently asked questions

›How can I check if a port is open without installing anything?

Use the tool above: enter the hostname or public IP and the port number, and you get an answer in seconds from a real TCP connection attempt — no telnet, nmap or command line needed.

›What is the difference between “closed” and “timeout”?

“Closed” means the host actively refused the connection — the machine is online but no service listens on that port. “Timeout” means no reply at all, which almost always indicates a firewall silently dropping the traffic (or a host that is offline).

›The port is open locally but closed from here. What now?

Check, in order: (1) the service binds to 0.0.0.0 and not 127.0.0.1, (2) the OS firewall (ufw, firewalld, Windows Firewall) allows the port, (3) your cloud security group or router forwards it, (4) your ISP doesn't block it. Re-test after each change.

›Can I use this to test if my ISP blocks a port?

Yes. If a service is confirmed running and reachable from elsewhere, but times out when tested against your home connection's public IP, your ISP or router is likely blocking it. Port 25 is blocked by most residential ISPs, for example.

Related tools

Port Checker

The core TCP port test with latency measurement.

Open Port Checker

Audit your server's exposed ports from outside.

SSL Checker

Port 443 open? Verify the certificate next.