Network

Online Port Scanner / Checker

Test if a TCP port is open and accepting connections from our server — check web, mail, SSH or any custom port remotely.

About Port Check

Tests whether a specific TCP port on a host is open and accepting connections from our server. Useful for confirming a firewall rule actually took effect, checking that a service is listening on the port you expect, or verifying a port is properly closed as part of a security review. A closed or filtered result doesn't mean the same thing — closed means the host actively refused the connection, while filtered/timeout usually means a firewall is silently dropping the packets.

Scanning ports on infrastructure you don't own or have permission to test can trigger automated abuse alerts on the target network — this is intended for checking your own infrastructure or hosts you're authorized to test.

📖 Read more in our Knowledge Base →

Note

Tests TCP connectivity from our server, not your browser. A port may be open to us but firewalled for you, or vice versa.

Private IP ranges (10.x, 192.168.x, 172.16-31.x) are blocked.

Related Tools

Open, closed or filtered

ResultWhat happenedWhat it usually means
OpenThe TCP connection was accepted.A service is listening and the firewall lets our server through.
ClosedThe host answered with a refusal.The host is reachable, but nothing listens on that port.
Filtered / timeoutNo answer at all.A firewall is silently dropping the packets, or the host is down.

For common services (FTP, SSH, SMTP, POP3, IMAP, MySQL, PostgreSQL, Redis, MongoDB) the tool also shows the greeting banner the service sends, which often reveals the software and version. This tool tests TCP only, from one location: our server.

Common ports

PortService
22SSH
25SMTP between mail servers
465 / 587SMTP submission from mail clients (implicit TLS / STARTTLS)
80 / 443HTTP / HTTPS
993 / 995IMAPS / POP3S
3306 / 5432MySQL / PostgreSQL
3389Windows Remote Desktop

Open on the server, closed from here

  • Listening on localhost only. A service bound to 127.0.0.1 can't be reached from outside. Check with ss -tlnp on Linux or netstat -an on Windows.
  • Host firewall: ufw, firewalld, iptables/nftables or Windows Firewall.
  • Cloud firewall: security groups and network ACLs sit in front of the server.
  • Home connections: the router needs port forwarding, and carrier-grade NAT (CGNAT) makes inbound connections impossible. Many ISPs also block port 25 on residential lines.

Ports that should be closed

Databases and caches (3306, 5432, 6379, 27017) should never answer from the internet. Exposed Redis and MongoDB instances are a common cause of data breaches. Restrict them to a private network or an allow-list.

Test from your own machine

  • Linux / macOS: nc -vz example.com 443
  • PowerShell: Test-NetConnection example.com -Port 443