Ping Tool
Check whether a public host accepts TCP connections on port 80 from our server. The tool makes four separate connection attempts, allows up to three seconds for each one and reports the connect time of every success. This is a TCP port check, not an ICMP echo, an HTTP request or a measurement from your device.
How to run the TCP check
-
1
Enter a public host
Use a domain such as `example.com` or a public IPv4 address. A URL scheme, path and explicit port are ignored; the check always uses port 80.
-
2
Start the check
Our server resolves the host, rejects private, loopback, link-local and other non-public targets, then makes four TCP connection attempts.
-
3
Review each attempt
A successful row shows how long the connection call took. A failed row shows the socket error returned by the server.
-
4
Use the summary carefully
Minimum, average and maximum use successful attempts only. The displayed loss percentage is the share of connection attempts that failed; it is not measured IP packet loss.
What this check actually sends
Classic ping sends ICMP Echo Request packets and measures their replies. This tool does something different: the application server calls connect() for TCP port 80. It does not send an HTTP request, inspect a status code or fetch a page.
A successful attempt proves that a TCP connection to port 80 was accepted from our server at that moment. It does not prove that HTTPS on port 443 works, that the website returns valid content, or that the service is healthy for users in another region. A failed attempt is also narrower than “the host is down”: port 80 may be closed or filtered while another service remains available.
Reading the results
| Result | Exact meaning | What it does not establish |
|---|---|---|
| Attempt time | Time spent resolving or opening that TCP connection, shown in milliseconds | ICMP round-trip time or page-load time |
| Minimum | Fastest successful attempt | A guaranteed baseline for every visitor |
| Average | Mean of successful attempts only | An average that includes failed attempts |
| Maximum | Slowest successful attempt | The cause of a delay or a routing change |
| Loss | Percentage of the four TCP connection attempts that failed | Network packet-loss percentage |
With only four samples, differences between the minimum and maximum can show that connect times varied, but they are not enough to diagnose congestion, Wi-Fi, routing or packet loss. Repeat the check and use dedicated network diagnostics if you need to investigate the path.
Why an attempt can fail
- The name cannot be resolved: the initial DNS lookup returned no public address, so the connection test does not start.
- Connection refused: the target answered, but no service accepted the TCP connection on port 80.
- Timeout or another socket error: a firewall may be dropping the connection, the route or target may be unavailable, or the attempt may have exceeded its three-second limit.
- Only public targets are allowed: private, loopback, link-local, reserved and other non-public addresses are blocked. If a hostname resolves to any blocked address, the tool rejects it.
The four attempts run on our server, not in your browser. Consequently, the hostname is sent to the server for processing, and the result describes connectivity from the server’s network. In the two-step interface, the hostname can also appear in the page URL. Do not enter internal or sensitive hostnames.
Scope and limits
This is a one-off port 80 check with four attempts and a three-second timeout per attempt. It has no traceroute, continuous monitoring, history or export, and it cannot test a custom port. Use an HTTP status checker when you need an actual HTTP response, a DNS lookup tool when you need records, and a monitoring service when you need checks over time and from multiple locations.
Frequently Asked Questions
No. The usual ping command uses ICMP Echo Request and Echo Reply. This tool opens TCP connections to port 80 from our server and times the connection calls. The two tests can produce different outcomes because firewalls and services treat ICMP and TCP differently.
It only means port 80 accepted a TCP connection from our server. The tool does not request a page or verify an HTTP status, content, TLS certificate or port 443. Use an HTTP checker or open the site separately to test those layers.
Your browser may use HTTPS on port 443 while this tool always tests port 80. The target may also filter our server, or connectivity may differ by location. A refused connection, a timeout and a DNS failure are different conditions, so check the displayed error.
It is the percentage of four TCP connection attempts that did not succeed: 0%, 25%, 50%, 75% or 100%. It is labelled loss in the interface, but it is not a direct packet-loss measurement and should not be interpreted as an ICMP packet-loss rate.
No. The tool accepts public internet hosts only and always connects to port 80. It blocks private, local and reserved address ranges to prevent the server from being used to reach internal services.
Related Tools
What Is My IP
See the IP address this server received for your request, its IPv4 or IPv6 family, and an approximate country when local GeoIP data is available.
IP Address Lookup
Look up any public IPv4 or IPv6 address for approximate country, region, city, coordinates, ISP, ASN, organization and timezone.
Speed Test
Run a fast, free, browser-based internet speed test. Measure your download speed in Mbps plus round-trip latency and jitter, and see whether your connection is ready for 4K streaming, gaming and video calls, no app, no signup.
DNS Lookup
Query the A, AAAA, MX, TXT, NS, CNAME and SOA records of any domain without opening a terminal.
Reverse DNS Lookup
Look up the PTR record for an IPv4 or IPv6 address. Useful for mail-server debugging, log analysis and spam-filter investigations.
WHOIS Lookup
Look up public WHOIS registration data for a domain: registrar, nameservers, status codes and expiry dates.
Tool available in other languages
- 핑 도구 [KO]
- Pingverktyg [SV]
- أداة Ping [AR]
- Narzędzie ping [PL]
- Ping-Tool [DE]
- Outil de ping [FR]
- เครื่องมือ Ping [TH]
- Alat Ping [ID]
- Pingtool [NL]
- Pingツール [JA]
- Công cụ ping [VI]
- Ferramenta de ping [PT]
- Herramienta de ping [ES]
- Strumento ping [IT]
- Ping 工具 [ZH]
- Проверка соединения Ping [RU]
- Ping aracı [TR]