Online Ping & Port Checker

Test server availability and scan for open ports. Diagnose connection timeouts, firewall rules, and latency issues from an external node.

EN TR RU

Input

Host
Ports

Output

Diagnosing Connectivity: Beyond the Browser

When a website fails to load or a database connection drops, the browser's "Connection Timed Out" error is vague. The problem could be DNS, a down server, or a blocked port. Our Ping & Port Checker acts as an external diagnostic node. It attempts to establish a TCP Handshake with the target IP address on specific ports (like 80 for Web, 22 for SSH). Unlike a local ping from your command line, this test originates from our remote servers, verifying if the host is reachable from the public internet, bypassing local cache or network quirks.

Understanding Port States: Open, Closed, and Stealth

In network security, the status of a port reveals the server's posture. An Open port accepts connections (danger if unintended). A Closed port actively rejects connections (RST packet), meaning the server is up but the service is down. A Filtered (Stealth) port simply drops packets, resulting in a timeout. This is the hallmark of a properly configured Firewall dropping unauthorized traffic. Use this tool to verify if your `iptables` or cloud security groups (AWS Security Groups) are correctly whitelisting traffic to your services.

Troubleshooting Home Servers and Gaming

Running a Minecraft server or a Plex media server from home requires "Port Forwarding" on your router. However, misconfigurations or ISP-level blocking (CGNAT) often break external access. By inputting your public IP and the service port (e.g., 25565 or 32400), you can definitively confirm if the outside world can reach your application. If the tool reports the port as closed, the issue lies within your router's NAT configuration or your ISP's restrictions, not the client trying to connect.

FAQ
Many servers and modern firewalls block ICMP (Ping) packets to prevent network discovery or Ping Floods, while still allowing traffic on port 80/443 (HTTP/HTTPS). This is why a TCP Port Check is often more reliable than a standard Ping.
Accurately checking UDP ports via the web is technically difficult because UDP is a "fire-and-forget" protocol; servers often don't send a reply if a port is open. This tool primarily tests TCP connectivity, which requires a handshake.
It means the request reached the target server, but the server said, "No service is listening on this port." This confirms the server is online and the firewall allowed the packet, but the specific application (like Apache or SSH) is stopped.
You can search for "what is my ip" on Google. Note that if you are behind a VPN or Proxy, you need to turn it off to find your true home/server IP address for port testing.
Port scanning your own infrastructure for diagnostic purposes is legal. However, scanning third-party networks without permission can be classified as a hostile act or a prelude to an attack. Always use this tool responsibly on assets you own or manage.