Your input is sent to our server to run the check. We don't log it. Public check targets and results may be cached temporarily to avoid repeating checks.
Enter a URL or hostname, up to 253 characters. A hostname uses HTTPS.
Response from our server
Ready to check
Enter an address and press Check.
- HTTP status
- Final response time
- Final address
Check a website’s response from our server.
How to use
- Enter a public website URL or hostname. Without a scheme, HTTPS is used.
- Press Check to send a request from our server.
- 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.
Sources
- IANA: HTTP Status Code Registry
- IANA: Hypertext Transfer Protocol (HTTP) Status Code RegistryUsed for: reference data
- IETF RFC 9110: HTTP SemanticsUsed for: definitions
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.
What do 502, 503 and 504 mean?
A server in front of the website, such as a proxy, answered, but the one behind it did not deliver: 502 means it got an invalid response, 504 that it got none in time. 503 means the site is temporarily overloaded or in maintenance.
Why does the check show 403 or 429 when the site works for me?
The site is up but turned this check away. 403 means the server understood the request and refused it, and 429 that it limits how many requests it accepts; many sites treat checks from servers this way.
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.
How long does the check wait, and how fresh is the result?
It waits up to 8 seconds for each request and follows at most five redirects. Checks of the same address are shared for 30 seconds, so a result can be that old; the check time shows when it ran.





