Check if an endpoint is alive and see its response time
Check if an API endpoint is alive. Paste a URL and get the HTTP status code and response time in milliseconds. The request does not originate from your browser. The address is sent to our proxy server, which makes the call to bypass CORS blocking. The server sends a GET request, follows redirects, and waits up to 10 seconds before marking the address as unresponsive. Besides the status, the content type and server name are displayed when available, and the last 10 checks remain in a list until you close the page. Internal addresses like localhost or 192.168.x are blocked.
Browsers block requests to domains that have not authorized them (CORS). Therefore, the address you entered is sent to our proxy server, which executes the request and returns only the status, response time, and a few headers.
No. There is no field for headers or a request body, and the check is sent without credentials. A protected endpoint will usually return a 401 or 403, which is also a sign that the server is alive.
The time is measured from our server, not your computer, and it includes any redirects along the way. A different location on the network yields a different time.
No. The server blocks addresses like localhost, 127.0.0.1, 10.x, 192.168.x, and .local domains, because the request comes from the internet and has no access to your network.
Unresponsive means 10 seconds passed without a reply. A network error means the connection failed completely, for example due to a non-existent domain or an invalid SSL certificate.
Klix could not load
Try reloading the page first. If a new version just went out, a reload fixes it straight away.
If reloading did not help, your browser may be too old. Klix runs the tools on your own device rather than on a server, so it needs a browser from 2022 or later. What to do: update Chrome or Firefox, then open klixtools.com again.