🌐My IP Address 🔌Port Checker 🔍DNS Lookup 📋WHOIS Lookup 🔒SSL Checker 🗺️IP Location Map 📡HTTP Headers Latency Test 🖥️User Agent 🔢IPv6 Detector
TCP Port Testing · No Download

Free Online Port Checker

Free online port checker. Test if any TCP port is open on any host or IP address — SSH (22), HTTP (80), HTTPS (443), MySQL (3306), PostgreSQL (5432), MongoDB (27017) or any custom port.

Port Checker
Enter a hostname or IP and the ports you want to test (comma-separated). Results appear in real time.
Enter a host and ports → click Check Ports
Advertisement

What is a port checker?

A port checker tests whether a specific TCP port on a remote host is accepting connections. When a port is "open", it means there is a service listening on that port and it is reachable from your current network. When a port is "closed" or "filtered", either no service is running on that port or a firewall is blocking the connection.

Common ports and their services

Why would a port appear closed?

A port can appear closed for several reasons: no service is listening on that port, a firewall (like AWS Security Groups, UFW, or iptables) is blocking the connection, or the host is offline. If you expect a port to be open, use our IP Whitelist Config Generator to add your IP to the relevant firewall rules.

How to check if a port is open from the command line

Without a port checker tool, you can test port connectivity directly from your terminal. On Linux and macOS, use nc -zv hostname port (netcat) or telnet hostname port. On Windows, use Test-NetConnection -ComputerName hostname -Port port in PowerShell.

For example, to check if port 443 is open on a server: nc -zv example.com 443. If the connection succeeds, the port is open. If it times out or refuses, the port is closed or blocked by a firewall.

What is the difference between TCP and UDP ports?

TCP ports (Transmission Control Protocol) require a three-way handshake before data is exchanged, making them reliable and ordered. Web servers (port 80, 443), SSH (port 22), and databases (MySQL port 3306, PostgreSQL port 5432, MongoDB port 27017) all use TCP.

UDP ports (User Datagram Protocol) send data without establishing a connection first. This makes UDP faster but less reliable. DNS (port 53), NTP (port 123), and gaming protocols commonly use UDP. This port checker tests TCP ports only, as UDP port testing requires a different approach.

Advertisement

Port checker questions

How does this port checker work?
This tool attempts TCP connections from your browser to the target host and port using WebSocket probing. A successful connection means the port is open. Results reflect what's reachable from your current network — results may differ if you're behind a corporate proxy or VPN.
What's the difference between closed and filtered?
A closed port actively refuses the connection (the server responds with a reset). A filtered port doesn't respond at all — typically because a firewall is silently dropping packets. Both appear as "Closed / Filtered" in this tool since the distinction requires raw socket access not available in browsers.
How do I open a port on my server?
It depends on your setup. For AWS EC2, add an inbound rule to your Security Group. For Linux servers, use UFW (sudo ufw allow 443) or iptables. For GCP, create a Firewall Rule. Use our IP whitelist config generator to get the exact commands for your environment.
What is the difference between TCP and UDP ports?
TCP ports establish a reliable connection before sending data, used by HTTP (80), HTTPS (443), SSH (22), MySQL (3306), PostgreSQL (5432), and MongoDB (27017). UDP ports send data without a handshake, used by DNS (53) and streaming protocols. This tool tests TCP ports.
How do I open a port on my Linux server?
Use UFW: sudo ufw allow PORT/tcp or iptables: sudo iptables -I INPUT -p tcp --dport PORT -j ACCEPT. On AWS, add an inbound rule to your Security Group. Always restrict access to your specific IP address instead of opening ports to 0.0.0.0/0.
Copied!