Skip to content

Is it down?

Web & developer

How is this website responding?

Check a website’s response from our server.

Enter a URL or hostname, up to 253 characters. A hostname uses HTTPS.

Response from our server

Ready to check a website

The check runs from our server.

  • HTTP status
  • Final response time
  • Final address

Sponsored Links

Check a website’s response from our server.

How to use

  1. Enter a public website URL or hostname. Without a scheme, HTTPS is used.
  2. Press Check to send a request from our server.
  3. Read the response, HTTP status, final address and check time.

How it works

The checker asks the website for a response from our server. It follows redirects and checks the final HTTP status. A 200 response means the request succeeded; a 404 or 503 still means a server answered, but with an error.

Response time measures the final server request, not earlier redirects or the full page load. For example, 120 milliseconds is 0.12 seconds. This does not test page scripts, sign-in or every visitor’s connection.

A timeout, blocked check or failed connection cannot prove the website is down for everyone. Results may be cached. Sources: RFC 9110 (HTTP methods and responses) and the IANA HTTP Status Code Registry.

Sponsored Links

Frequently asked questions

Why can I open the site when this check fails?

Your route may differ, or the website may block our server. This is one viewpoint.

Does HTTP 404 mean the whole website is down?

No. The server answered that the requested resource was not found. Other pages may work.

Is the response time a speed test?

No. It measures only the final response, not the full page download or rendering.

Does this monitor my website continuously?

No. Each check is a snapshot. It does not run scheduled checks or send outage alerts.

Can it check a page that needs a login?

No. It checks the public response without signing in. A reachable login page does not prove the pages behind it work.

Sponsored Links

Sponsored Links