Domain, hostname, IP address or URL

Only the host is used; URL paths and queries are discarded.

What this tool does

This tool observes a public host from two perspectives: a server in Bavaria sends ICMP packets, while your browser measures HTTPS latency to the host. The values stay separate because they represent different operations.

How to use the tool

Enter a domain, hostname, public IPv4 or IPv6 address, or an HTTP(S) URL.
Start the test and review the normalized target and the public IP address selected for ICMP.
Read the server ping and browser measurement as separate results.

Useful applications

Check basic reachability and the approximate response time of a public host.
See whether a host answers ICMP or whether a firewall may be filtering it.
Estimate HTTPS response latency from your own browser connection.
Make differences between a server-side view and your user connection visible.

Notes and limitations

The browser measurement uses several HTTPS HEAD requests to the root path and is not an ICMP ping. HTTPS includes more than the network path, including DNS, connection setup, TLS and the web server response.
No ICMP response does not prove that a host is offline because firewalls or systems may block ICMP.
Browser measurements can fail because of HTTPS certificates, browser rules or an unreachable connection, especially for direct IP addresses.
Individual latency values vary and are not a lasting availability guarantee. The tool pings only pre-validated public IP addresses and does not store a ping history.

Frequently asked questions

What is a ping?

A ping sends echo requests over ICMP and measures whether replies return and how quickly they arrive.

Why do server ping and browser latency differ?

They start from different locations and measure different workflows because HTTPS adds steps beyond an ICMP echo.

Why does a website not answer a ping?

Many websites or upstream firewalls allow HTTPS while blocking ICMP, so a missing ICMP response does not automatically mean an outage.

Why does browser measurement fail for some IP addresses?

An HTTPS certificate may be issued for a hostname rather than the entered IP address, or the browser may not permit the cross-origin connection.