Free tools / Open port checker
Open port checker
Check whether a TCP port is open on a hostname or public IP from 16 locations. Each city reports open, closed, or filtered, with the connect time.
Example result
example.com:443 · not a live checkOpen from 16 of 16 locations.
nc -vz -w 5 example.com 443
How the port check works
Each of the 16 locations resolves the hostname, refuses anything that is not a public address, and opens one TCP connection to the port. If the three-way handshake completes, the port is open; the connection is closed straight away and no bytes are sent. The locations are Ashburn, Columbus, San Francisco, Portland, Montreal, São Paulo, Dublin, London, Paris, Frankfurt, Stockholm, Tokyo, Seoul, Osaka, Singapore, and Sydney.
A check from your own laptop only proves the port is reachable from your network. Firewalls, security groups, and geo rules can allow one region and drop another, so a port can be open from Frankfurt and filtered from Tokyo. That shows up here as a partial result.
Open, closed, and filtered
| Result | What happened | Usual cause |
|---|---|---|
| Open | The handshake completed. | A service is listening and the path allows it. |
| Closed | The host answered with a reset (connection refused). | The host is up, but nothing listens on that port, or the service is bound to 127.0.0.1 only. |
| Filtered | Nothing answered within 3.5 seconds. | A firewall, security group, or router drops the packets, or the host is down. |
Common ports
| Port | Service | Should it be open to the internet? |
|---|---|---|
| 22 | SSH | Only if you need it. Restrict it by IP or put it behind a VPN or bastion. |
| 25 | SMTP (server to server) | On mail servers. Cloud networks often restrict outbound port 25, so results here can read filtered. Test 587 or 465 for submission. |
| 80 / 443 | HTTP / HTTPS | Yes, on web servers and load balancers. |
| 3306 | MySQL | Almost never. Keep databases on a private network. |
| 5432 | PostgreSQL | Almost never. Managed providers that expose it require TLS and a password. |
| 6379 | Redis | No. An open Redis port is a common way servers get compromised. |
| 3389 | Remote Desktop | No. Use a VPN or a gateway. |
| 8080 / 8443 | Alternate HTTP / HTTPS | If an app or proxy is meant to serve there. |
Checking from your terminal
From a shell, nc -vz does the same handshake from wherever you are. Compare it with the result above to tell a local firewall from a remote one.
nc -vz -w 5 example.com 443
# PowerShell
Test-NetConnection example.com -Port 443
Frequently asked questions
- Is this a port scanner?
- No. Each check tests one port on one host. Checks are limited per visitor and per host each minute, so the tool can't sweep a range of ports.
- Can I check the port forwarding on my home router?
- Yes. Enter your public IPv4 address and the forwarded port. Some ISPs block common inbound ports such as 25 and 80 on home connections, which shows up as filtered. Private addresses such as
192.168.x.xcan't be checked from the internet. - Why is the port open from some cities and filtered from others?
- A firewall or security group allows some source ranges and not others, geo blocking is on, or the hostname resolves to different servers in different regions. The resolved IP is shown with the result so you can compare.
- Does it check UDP or IPv6?
- Not yet. This page checks TCP over IPv4. A TCP check in the console can also use IPv6.
- How do I get told when the port stops answering?
- Add a TCP check. It connects on a schedule from the regions you pick, waits for three failed runs in a row by default before it marks the port down, and alerts you by email, Slack, Discord, PagerDuty, or webhook. You can also set it to expect the connection to fail, which catches a database port that was opened by mistake.
Know when the port stops answering
QuickStatus.dev TCP checks connect to your host and port on a schedule, confirm a failure before they open an incident, and alert you by email, Slack, Discord, PagerDuty, or webhook. Free for 10 checks every 5 minutes from 1 region, no card.