Ping & Port Checker

Test if specific TCP ports are open or closed, run ping response diagnostics, and measure host connection latency.

Ping & Port Checker

Diagnose network connectivity. Test if specific TCP ports are open or closed, measure connection latency, and check host response status.

Port Check Settings

Common Ports:

Port 443: HTTPS (Secure Web Server)

Ping Settings

Diagnostic Output Console

> Diagnostic monitor offline. Enter settings and click check to initiate diagnostic check.

Understanding Network Ports and Diagnostics

The Ping & Port Checker is a diagnostics tool designed to check the online status of a target domain or IP address, as well as inspect if specific TCP ports are receptive to connection handshakes.

To understand network ports, it helps to use the apartment building analogy:

  • An IP Address is the building’s street address, pointing to the specific physical server on the internet.
  • A Port is like an individual apartment number or mailbox. A single server can run many services (web server, email server, database), and each service is assigned to a specific port so incoming network packets know exactly which service to talk to.

Port Status Definitions

When you scan or check a port, it will return one of three states:

Status Meaning Security Implication
Open The server is actively running a service on this port and has completed the TCP three-way handshake connection. Receptive to traffic. Ensure the running service is fully updated and secure.
Closed The target host is online, but no active service is listening on this port. The server actively rejected the connection request. Normal state for unused services. Safe from external connections.
Filtered (Blocked) The connection attempt timed out. No response was returned. This usually means a firewall is dropping the packets silently. Indicates a protective firewall (like UFW or Cloudflare) is actively filtering traffic.

Common TCP Ports and Their Functions

Modern servers run multiple standardized services. Below are some of the most common ports checked by developers and IT administrators:

  • Port 80 (HTTP): Used for unencrypted, plain text web pages.
  • Port 443 (HTTPS): Used for secure web pages encrypted with SSL/TLS.
  • Port 21 (FTP): Used by File Transfer Protocol for sending and receiving files.
  • Port 22 (SSH): Used for Secure Shell to remotely access and manage a server terminal.
  • Port 25 (SMTP): Used by mail servers to route outgoing email.
  • Port 53 (DNS): Used to translate human-friendly domains into IP addresses.
  • Port 3306 (MySQL): Used to connect to MySQL database servers.
  • Port 3389 (RDP): Used by Windows Remote Desktop Connection.

What is a TCP Ping?

Standard network ping diagnostics use ICMP (Internet Control Message Protocol) echo request packets to measure round-trip times. However, many modern hosting providers, cloud servers, and firewalls are configured to block ICMP packets to prevent denial-of-service (DoS) sweeps, causing standard ping tests to fail even when a website is fully online.

A TCP Ping solves this by establishing a standard TCP connection on a specific port (typically port 443 for secure web hosts or port 80). Because servers must accept web requests on these ports to function, TCP pings bypass ICMP firewalls, providing a highly reliable connectivity check.

Network Troubleshooting Steps

If your port check reports a port is closed or timed out when it should be open, follow these troubleshooting steps:

  1. Verify Local Service Status: Ensure the service (e.g. Nginx, Apache, or MySQL) is running on the host machine.
  2. Audit Host Firewall (OS level): Verify that local firewall rules (like iptables or ufw on Linux, or Windows Defender Firewall) are configured to allow inbound traffic on that port.
  3. Configure Router Port Forwarding: If the server is behind a local router, check that port forwarding rules are correctly sending traffic on the target port to the server’s local private IP address.
  4. Check ISP Port Blocks: Some Residential ISPs block inbound traffic on standard web ports (like port 80 or 25) to prevent home server hosting or spam routing. You may need to run your service on a non-standard alternative port (like 8080).

Limitations & Restrictions

To maintain security and integrity, the following restrictions apply to this online utility:

  1. No Private or Local Networks: You cannot check private IP addresses (such as 127.0.0.1, 10.x.x.x, 192.168.x.x, or 172.16.x.x) or local hostnames (like localhost or .local domains). Tests are executed from public cloud servers, which cannot access private local networks.
  2. Port 25 (SMTP) is Blocked: Outbound connections on port 25 are blocked at the network level by Cloudflare to prevent email spam abuse. If you need to test mail server connectivity, please use alternative ports like 465 or 587.
  3. Cloudflare Firewalls: If the target server blocks traffic originating from Cloudflare Edge IP addresses, the diagnostic checks will report the ports as closed or filtered.

Frequently Asked Questions (FAQ)

What is the difference between a standard Ping and a TCP check?

A standard Ping uses ICMP (Internet Control Message Protocol) packets to check if a server is alive. A TCP check establishes a handshake connection on a specific TCP port (like 80 or 443). Since many firewalls block ICMP packets to prevent sweeps, TCP checking is often more reliable for testing web servers.

Why does a port status show as “Filtered” instead of “Closed”?

  • Closed means the server is online but actively refused the connection because no service is listening on that port.
  • Filtered (Timed Out) means no response was received at all. This usually indicates that a firewall (such as UFW, AWS security groups, or Cloudflare) is silently dropping packets before they reach the server.

Why can’t I ping local IP addresses like 192.168.1.1 or 127.0.0.1?

These are private local IP addresses reserved for internal networks. Because this tool runs on public cloud servers, it cannot look inside your home or office local network. To test local IPs, you must use command-line tools (like ping or telnet) on your local machine.

Can I check multiple ports at the same time?

No. To prevent abuse, rate-limiting triggers, and keep resource usage low, the tool is designed to verify one port at a time.

Does this tool support UDP ports?

No, this tool only supports TCP ports. UDP is a connectionless protocol and cannot be easily verified via standard edge-network handshakes without sending protocol-specific payloads.