Responding
A successful response was returned from the checked page, including any safely followed redirects.
Find out whether a website is responding from our server. Get a clear result, HTTP status code, and useful next steps in seconds.
Websites can fail in different ways. We make the response understandable so you know what to try next.
A successful response was returned from the checked page, including any safely followed redirects.
An HTTP 4xx code means the server answered, but the requested resource or access was denied.
An HTTP 5xx code indicates that the web server responded with an error.
A connection or DNS failure means our server could not complete the request. Other regions may differ.
The problem might be your internet connection, browser cache, DNS settings, VPN or local network. Our result is a clue, not a claim about every country.
Follow the troubleshooting guideSwitch between Wi-Fi and mobile data to rule out a local network problem.
Test whether extensions, stored cookies or your browser cache are interfering.
Some failures are temporary. A single test cannot establish a worldwide outage.
We test the website from our server. If it responds for us but not for you, the issue might be local or regional. If it does not respond for us, it may be down, blocked, or unreachable from our network. This is not a worldwide test.
Yes. You can check public website addresses without registering or paying. To protect websites and our hosting, we apply short-term caching and reasonable request limits.
HTTP 403 means access is forbidden; HTTP 404 means the page wasn't found. Both indicate that a server responded. They do not prove that the entire website is offline. Read the status code guide.
Checks are carried out when you request them. We temporarily reuse results for up to 45 seconds to avoid sending unnecessary repeated requests to other websites. The result displays when it was checked.
Ads are not enabled. This area is reserved for a clearly labelled ad after approval and consent setup.