It is a remote HTTP/HTTPS check that reports availability, status codes, response headers, resolved IP addresses, and request timings from global locations.

HEAD, GET, and OPTIONS are supported.

The report includes total time, DNS lookup, TCP connection, TLS handshake, time to first byte (TTFB), and download time.

HTTPS is supported automatically. The Globalping probe network can negotiate HTTP/2 when the target and measurement protocol support it; the current NetUtils form selects HTTP or HTTPS based on the entered URL.

For HTTPS, TLS timing shows how long the secure handshake took. For plain HTTP, no TLS handshake is performed.

2xx indicates success, 3xx indicates redirection, 4xx indicates a client-side request error, and 5xx indicates a server error.

Headers are metadata exchanged with the response, such as content type, cache policy, server information, redirects, and security directives.

Enter the URL, select HEAD for a lightweight headers-only request, run the test, and inspect “Response headers” for each location.

TTFB is the time between sending the request and receiving the first byte. It includes network latency and the server’s initial processing time.

Redirect handling is performed by the Globalping HTTP measurement engine. The returned status and raw response show whether the request reached a redirect or a final destination.

You can test publicly reachable HTTP/HTTPS hosts. Private, local, malformed, or network-blocked addresses may be rejected or time out.

HEAD requests headers without downloading the response body. GET requests the full resource and can therefore include meaningful download timing.

Use it to verify availability, diagnose regional failures, inspect headers and status codes, and identify slow DNS, TCP, TLS, TTFB, or download stages.

No. Requests run from distributed Globalping probes in the selected locations.