What does the connectivity tester do?

It sends an HTTP request to the URL you provide and reports whether the server responded, how long it took, the status code returned, and a summary of the response headers.

How is the test made?

The request goes through a ToolboxHub server endpoint, which makes a HEAD request (with GET fallback) to the destination URL. This bypasses browser CORS restrictions and gives an accurate measurement of total latency from the server.

Is this an ICMP ping?

No. The traditional ping uses ICMP packets, which can't be sent from the browser or HTTP server. This tester is a proxy of HTTP/HTTPS reachability — more useful in practice for measuring website and API availability.

Why test from the server and not the browser?

From the browser, most requests are blocked by CORS or return 'opaque' responses, which prevent reading the status and headers. By going through our server, we can show all this data accurately.

Does it work with HTTP and HTTPS?

Yes. The tester accepts both HTTP and HTTPS. When the protocol is omitted, it assumes HTTPS automatically. Internal hosts (localhost, private IPs) are blocked for security reasons.

What does it mean when the response is 4xx or 5xx?

It means the server received the request but returned an error. 4xx indicates a client-side issue (URL not found, no permission), while 5xx indicates a problem on the destination server. The site may even be online — just not for that URL.

Does it follow redirects?

Yes. The tester follows up to the standard limit of redirects and reports the final URL where it landed, along with a 'Redirected' badge whenever the original URL pointed somewhere else.

Free Online Connectivity Tester: Ping URL, Latency & HTTP Status

About the Connectivity Tester

Check whether a website or API is reachable, measure the response time in milliseconds and see the HTTP status and main response headers. Useful for debugging integrations, monitoring deployments, and quickly diagnosing whether a service is down or just slow. To inspect the IP behind a host, use our IP Lookup.

How to test in 3 steps

1Type the URL — for example https://example.com — or pick a preset.
2Click Test to send a HEAD request through ToolboxHub's server.
3Read the status, latency and headers. The tested URLs are listed in the history.

What does each HTTP status mean?

Status codes are organized into ranges. The summary below helps you quickly interpret the result.

Range	Meaning	Examples
2xx	Success — request handled correctly	200, 204
3xx	Redirect — the resource is in another URL	301, 302, 308
4xx	Client error — invalid URL, no auth, blocked	401, 403, 404
5xx	Server error — failure on the destination side	500, 502, 503