WEB FAULT BENCHPUBLIC WEBSITE DIAGNOSTICSTOOL / 003
WHY IS MY SITE DOWN?

Find the
failing layer.

One public host. Three checks.
Read the evidence before you change the settings.

Checks the root address. Paths, query parameters and fragments are discarded. Never enter a password or private link.

DIAGNOSTIC WORKBENCHREADY FOR A PUBLIC HOST

Start with a site address.

We’ll separate the DNS lookup, secure connection and server response.

01

DNS / ADDRESS

Can the host be resolved to a public address?

Details
No check run yet.
WAITING
02

HTTPS / CONNECTION

Does its secure connection verify?

Details
No check run yet.
WAITING
03

HTTP / RESPONSE

What does the server return for its root?

Details
No check run yet.
WAITING

A successful response from this checking server does not prove that every visitor, account, path or region can access the site. A timeout or blocked probe does not prove a global outage.

READ THE RESULT

Fix the layer
that failed.

01 / DNS

Check the destination first.

Confirm the hostname, authoritative DNS records and nameservers with your provider. A recently changed record can take time to become visible. A failed lookup here describes this check’s result.

02 / HTTPS

Check certificate and hostname.

A certificate error can come from expiry, a mismatched hostname or an incomplete chain. Check your host’s certificate setup before switching off security protections.

03 / HTTP

Read the actual response.

A 5xx response points to a server or upstream error. A 401, 403 or 429 can be authentication, protection or rate limiting. A root check does not test every page, login or checkout.