Read the failing layer before changing a website setting
The Web Fault Bench checks the public root of a host and keeps DNS, HTTPS and HTTP evidence separate. A result from this checking path helps choose the next setting to inspect; it is not a universal outage verdict.
Use the host you intend to check
The root check discards the entered path, query and fragment. It does not test a particular login, checkout or page. Private and unsupported destinations are refused; redirects are rechecked.
Follow the reported layer
- For DNS, compare the hostname and authoritative records before changing unrelated settings.
- For HTTPS, read whether the platform connection completed or remained unknown; review your hosting certificate configuration without turning off verification.
- For HTTP, inspect the actual response: 5xx can indicate a server or upstream issue, while 401, 403 or 429 can reflect access control, protection or rate limiting.
Keep transport limits visible
The tool uses a bounded HEAD request and does not download a page body. Cloudflare performs the connection resolution independently after public DNS checks. The application does not expose the connected IP, certificate chain, issuer, expiry or a proxy's hidden origin connection.
Compare another relevant observation
An unknown, blocked or timed-out probe does not prove that the site is offline. A successful root response does not prove that every visitor, account, region or application route can use it. Keep the check time and the actual response with the next provider-side investigation.
Keep the limit in view
This guide makes no uptime guarantee or certificate audit claim. Platform HTTPS completion and unknown failures must retain their actual meanings; there is no insecure retry. No submitted host or diagnostic result is passed into the advertising panel.