Logo
Port checker·23 common ports

Which ports are actually open?

Test any public server against the most commonly used TCP ports — web, mail, database, and remote access — and see what's reachable from the internet.

Live TCP connect
Public hosts only
Enter a host to check its open ports.
Try google.com, github.com, or your own server.
What you get

Open ports, at a glance.

We attempt a live TCP connection to each port and report exactly what came back — no guessing, no cached results.

Live TCP connect

Every port is tested with a real connection attempt from our servers, timed and reported as open or closed.

23 common services covered

Web, mail, database, remote access and more — FTP, SSH, HTTP(S), MySQL, PostgreSQL, RDP, Redis, MongoDB and others.

Public hosts only

Requests are validated against private and reserved IP ranges before connecting, so this tool can only reach public infrastructure.

Instant results

All ports are checked in parallel with a short timeout, so a full sweep typically finishes in a couple of seconds.

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.

Start checking now Learn more
1,147
TLDs
200ms
Avg lookup
100
Suggestions/query
FAQ

Port checking, explained.

It means something on that server accepted a TCP connection on that port — usually a running service like a web server, mail server, or database. "Closed" means either nothing is listening, or a firewall is blocking the connection.
To confirm a service is actually reachable from the internet after deploying it, or to spot services you forgot were exposed — a database or admin panel left open to the public is a common misconfiguration worth catching early.
Scanning all 65,535 ports is slow, and a fast full scan looks identical to malicious reconnaissance from the target's perspective. Checking the ~23 most commonly used service ports covers the vast majority of real-world use cases quickly and responsibly.
No — this tool only connects to hosts that resolve to a public IP address. Private networks, localhost, and cloud-internal addresses are blocked before any connection is attempted.
Not by itself — plenty of services are meant to be open (80, 443). It's worth a second look when a port for something sensitive, like a database or remote-desktop protocol, is reachable from the public internet without you expecting it.