Ping Tool

Our server opens a TCP connection to the host and port you enter and reports how long it took. A reachability check from outside your network, not an ICMP ping.

What this ping tool does

When you press Ping Host, our server looks up the IPv4 address of the name you entered, opens a TCP connection to it on the port you chose (80 unless you change it), and reports how long the connection took. It then closes the connection without sending any data. The whole check is one TCP handshake, the same first step a browser takes before it requests a page.

This is not the ICMP ping you run from a terminal. The ping command sends ICMP echo requests, which many servers, firewalls and cloud providers drop on purpose, so a healthy server can look completely unreachable to ping while its website works fine. A TCP connect test asks a more useful question: is something answering on this port? The trade-off is that a host which answers ICMP but runs nothing on the port you chose will show as timed out here.

The connection is made from our server, not from your computer. That is useful when you want to know whether a host is reachable from outside your own network, but it means the time shown is our server's round trip to the target, and yours may be very different.

Reading the result

Each check ends in one of four ways. Here is what each one tells you, and what it does not.

Target reachable

What happened: the host accepted the connection on that port. Something is listening there.

About the time: it is the round trip between our server and the target, measured once. Compare it with earlier results for the same host rather than against a fixed threshold; the distance between the two machines matters more than anything else.

Connection refused

What happened: the host is online and answered, but with a reset: nothing is listening on that port.

What to check: the port number, and whether the service is running. Sites that only serve HTTPS answer on 443 and may refuse 80.

Connection timed out

What happened: nothing came back within 3 seconds.

What it can mean: the host is offline, a firewall is silently dropping packets to that port, the port is wrong, or the host blocks connections from our server's network. From the outside, these cases look identical.

Could not resolve hostname

What happened: the name has no IPv4 (A) record that our server could find. Hosts with only an IPv6 (AAAA) record fail this way, because the lookup is IPv4 only.

What to check: run the name through the DNS Checker to see which records exist.

What a successful ping does not prove

An accepted connection means the operating system on the target accepted a TCP connection on that port. It does not mean the application behind it is healthy: a web server can accept connections and still return errors, and a stuck application behind a proxy looks perfectly reachable. To see the HTTP status code and redirects a URL actually returns, use the URL Checker.

The check is a single attempt, so it says nothing about packet loss or how the latency varies. It tests one port at a time, IPv4 only, and only from our server's location. If you want to know whether a port on your own router is reachable from the internet, the Open Port Checker makes the same kind of connection with your public address filled in for you.

Which port to test

Use the port the service actually listens on. These are the usual defaults; the full list is the IANA Service Name and Port Number Registry.

Port Service Notes
80HTTPPlain web traffic. Many sites keep it open only to redirect to 443.
443HTTPSEncrypted web traffic; the port to try first for any website.
22SSHServer administration and SFTP.
25SMTPMail delivery between servers. Often blocked by consumer ISPs.
53DNSMost DNS uses UDP, which this tool cannot test; TCP 53 is used for large answers.
3306MySQLDatabase connections. Usually closed to the internet on purpose.
8080HTTP alternateDevelopment servers, proxies and application containers.
21FTPLegacy file transfer, unencrypted.

Frequently asked questions

Why does the ping fail on a website that is working?

Usually one of three things: the site only answers on 443 and you tested 80; a firewall or CDN drops connections from addresses it does not recognise, including our server; or the name resolves only over IPv6. Try 443 first, then check the DNS records.

What is a good response time?

There is no single number. Distance matters most: Cloudflare's explanation of latency gives the example of a server in Ohio answering users 100 miles away in 5 to 10 milliseconds and users 2,200 miles away in 40 to 50. Judge a result against earlier results for the same host, not against a scale.

Can I ping an IPv6 address?

No. Hostnames are resolved to IPv4 only, so a name with only AAAA records returns "Could not resolve hostname", and a literal IPv6 address times out because our server does not connect over IPv6.

Is it safe to use this on any host?

The tool opens one TCP connection and closes it without sending data, which is what any client does before talking to a service. The target sees a single connection attempt from our server's address in its logs. It does not scan port ranges or multiple hosts, and you should only test hosts you run or are allowed to check.