How to use the website status checker
The website status checker makes a live request to a public hostname and reports whether the destination responds, which protocol and status it returns, and how long the request takes. It is a quick availability check from Nach-Welt infrastructure, not a substitute for distributed uptime monitoring.
Good reasons to use it
- Confirm whether a launch or deployment is reachable from outside your own network.
- Separate an origin outage from a browser-cache or local DNS problem.
- Capture the response code and timing before escalating a hosting incident.
A reliable workflow
- Enter the hostname without a path or private credentials.
- Run the check and note the final response, timing and any redirect.
- Compare the result with your origin, CDN and monitoring dashboard.
How to interpret the result
A 2xx response usually means the endpoint answered successfully. A 3xx response means another location was returned. A 4xx response points to a client, access or missing-resource condition, while a 5xx response points to a server or upstream failure. One successful request does not prove continuous availability.
Frequently asked questions
Does a 200 response mean the whole website is healthy?
No. It confirms one request succeeded. Application functions, logged-in areas, assets and other locations may still fail.
Why does the result differ from my browser?
The checker uses a different IP address, DNS path, user agent and cache state. CDN or security rules may treat it differently.