What the Port Checker does
A port checker tests whether a specific TCP port on a host is open, closed, or filtered. Ports are the numbered endpoints services listen on — 80 for HTTP, 443 for HTTPS, 22 for SSH — and knowing which are reachable is essential for troubleshooting connectivity and reviewing exposure.
Because a browser cannot open raw TCP sockets for security reasons, live scanning must be done from your own machine. This tool gives you the precise nmap and telnet commands for your target, along with a guide to reading the results and a reference of the ports that matter most.
How to read a port's state
- open — a service is actively listening and accepting connections on that port.
- closed — the host responded but nothing is listening on that port.
- filtered — a firewall is silently dropping probes, so the state can't be confirmed.
- Common ports: 22 SSH · 25 SMTP · 53 DNS · 80 HTTP · 443 HTTPS · 3306 MySQL · 3389 RDP.
Worked example
Input: example.com
nmap -p 80,443,22,21,25 example.com telnet example.com 80
Run the nmap command to scan several ports at once, or use telnet for a quick single-port check — a blank screen means the port is open, while an immediate refusal means it's closed.
Common use cases
- Confirm a web, SSH or database server is actually listening on its port.
- Diagnose whether a firewall is blocking a connection.
- Verify port-forwarding rules on your router are working.
- Audit which services are exposed on a host you administer.