Nomlen logo
Free port tool· TCP scan of 23 common ports

Port checker test any open port free

Test 23 common TCP ports on any public server — live connection attempts, instant open/closed results.

Live TCP connectPublic hosts onlyNo login needed
See which ports a host leaves open
Try google.com, github.com, or your own server.
What you get

A full port scan, without the terminal

Test connectivity the way the internet sees it — from outside your network.

23 common ports

Scan the 23 ports that matter most — 80, 443, 21, 22, 25 and more — or check a single custom port for the service you run.

Port forwarding tester

Confirm your router actually forwards traffic to your machine — essential for game servers, cameras and self-hosted apps.

Open, closed or filtered

Each port is reported as open, closed or filtered, so you know whether a service is reachable, refused, or blocked by a firewall.

Public hosts only

The checker tests public hosts from the outside — the same view a visitor or attacker has — so nothing inside your network is probed.

Stop second-guessing.

Find your domain in the next 30 seconds.

Free forever. No login required. 1,100+ TLDs in one query — plus AI suggestions and the premium marketplace.

1,147
TLDs
200ms
Avg lookup
100
Suggestions/query
FAQ

Open port checker FAQs

Enter the host in a port checker: it attempts a real TCP connection to each port and reports open or closed. This page tests 23 commonly used ports in parallel and finishes in a couple of seconds. Closed results are just as useful — they confirm your firewall is doing its job.
Something on that server accepted a TCP connection on that port — usually a running service like a web or mail server. Closed means nothing is listening, or a firewall blocked the attempt before it reached a service. Unexpected open ports deserve a second look; expected ones are business as usual.
To confirm a newly deployed service is actually reachable, or to catch what you left exposed — a database or admin panel open to the public internet is a common misconfiguration worth finding early, before someone else does. Run the check after every deploy that touches networking or firewall rules.
Scanning all 65,535 ports is slow and looks identical to malicious reconnaissance from the target's perspective. The 23 most-used service ports cover the vast majority of real checks quickly and responsibly. The covered services — web, mail, database, remote access — account for nearly every legitimate check.
A closed port is reachable, but no application is accepting connections on it; the host actively refuses the attempt. A filtered port produces no useful response because a firewall or network device is dropping or blocking the probe. Closed usually points to the service itself, while filtered points to a rule between the checker and the host.
Local access only proves that the service is listening on the device. Internet access also needs a public address, correct router forwarding if NAT is used, an allowed host-firewall rule and no block by the internet provider. Carrier-grade NAT is a common hidden obstacle: the router may show a forwarding rule while the provider gives the connection no independently reachable public IPv4 address.
No. Public websites need ports such as 80 and 443 open. Risk comes from exposing services that were not meant to be public, running outdated software, or protecting an administrative service with weak credentials. Review each open port deliberately: identify the service, confirm it belongs there, keep it updated, and restrict management and database ports to trusted networks whenever possible.