Website Health Report
DNS, SSL, HTTP and timing in one report.
Reading the stack
- Lit the layer answered
- Amber a warning to look at
- Cracked a problem in this layer
- Wireframe not reached
The beam is one request leaving our server in Newark, US and rising through each layer in turn. The plates on top are the six security headers.
Report
archiveofourown.org
Running…
Findings
Recent reports in this browser
Why the stack stops at Connection
What the website health report does
The website health report runs a full set of checks on one address and puts the answers on a single page. It looks up the domain in DNS, opens a connection, reads the security certificate, requests the page, follows any redirects and reads the page title. It then reviews six security headers and pulls the domain’s name server, mail and email-authentication records.
It’s a good first stop when a site feels wrong but you don’t know where to look: after moving to a new host, before a launch, or when someone asks you to look over their website. It shows which layer has the problem, so you know which tool to open next.
How to use the website health report
- Type a website address.
- Press Run report. It takes a few seconds, because every layer is checked in turn.
- Read the verdict first, then each layer. Use the links at the bottom to dig deeper into DNS, certificates, speed or email.
Understanding the results
The verdict says whether the site is reachable from our server, has problems or isn’t reachable. Below it, each layer is marked OK, Warning or Problem. A certificate with 14 days or fewer left gets a warning, and so does a server that takes more than three seconds to start answering. If the site redirects, a table lists each hop with its status code and time. A 403 or 429 still counts as reachable: the server answered, it just turned away an automated request.
The timing bar splits each request into looking up the name, connecting, the secure handshake, waiting for the first byte and downloading, so a slow layer stands out. Every certificate met on the way is shown, with who issued it and how many days it has left. Hosting, CDN and mail providers are recognised from addresses, names and headers: that’s our rule of thumb, not proof.
The security headers score counts how many of the six are present, from 0 to 6. X-Content-Type-Options only counts when it says nosniff, and a Content-Security-Policy with frame-ancestors stands in for X-Frame-Options. In the DNS and email section, an empty MX line means the domain doesn’t receive email, and no CAA record means any certificate authority may issue certificates for it. For a closer look at the email records, use the SPF and DMARC checker.
Questions
What do the security headers mean?
They are optional instructions that make browsers safer when visiting the site. Missing ones are advice, not a failure; each row explains what the header does.
Can I check one page rather than the home page?
Yes. Paste the full address and the HTTP, redirect and content checks run against that page. The DNS and mail records always belong to the domain.
How long does the server have to answer?
We allow three seconds to open a connection and eight seconds for a response. A server that takes longer is reported as not answering.
Does a good report mean the site is up for everyone?
No. Checks run from our server in Newark, US, in one location, so results show what that location sees. It tells you the site works from there.
Do you store the report?
No. The report is built for you and not saved. A PDF report keeps a copy so anyone with its reference can open it. The Website Down Checker saves shareable results.