Tell the Advisor what's wrong. It runs the diagnostics and explains the results.

Give it a site and describe the symptom. It runs our uptime, SSL, DNS, header and health checks live, then walks through what they show and what to try next.

  • Live measurements, not a cached report
  • Backed by our guides and glossary, not guesswork
  • Each diagnostic shown on its own, in full

What it checks

Uptime and response

Reaches the site the way a browser would and reports the status code, response time and any redirect chain.

SSL certificate

Validity, issuer, expiry and which hostnames the certificate actually covers.

DNS records

The records that resolve for the domain, and anything that looks misconfigured.

Security headers

Which protective HTTP headers are present and which are missing.

Server health

A broader check of how the server is responding under the hood.

How it works

  1. You describe the problemGive it the site and a plain description of the symptom, the same way you would explain it to a colleague.
  2. It runs five checks at onceUptime, SSL, DNS, headers and health all run in parallel with their own timeout, so one slow check never blocks the rest.
  3. It reads the results against our knowledge baseThe written explanation is generated from the live measurements plus our verified guides and glossary; it will say so if the evidence is not enough to be sure.
  4. You get the full diagnostics, not just a summaryEvery check is shown in full underneath the explanation, in the same format as our individual tools, so you can verify the reasoning yourself.

Frequently asked questions

What does the Advisor actually check?

It runs five of our own diagnostics against the site you give it: an uptime and response check, the SSL certificate, DNS records, HTTP security headers, and overall server health. It reads the live results, not a cached report.

Is the explanation written by a person?

No. It is generated from the live measurements plus our verified guides and glossary, and is clearly a starting point, not a substitute for reading the full diagnostics below the summary or for a professional review of anything business-critical.

Why does one diagnostic sometimes fail while others succeed?

Each check runs independently with its own timeout, so a slow DNS resolver or a blocked port on one check does not stop the others from completing. A failed check is shown with its own error message.

Does this replace monitoring my site?

No. The Advisor runs once, when you ask it to. For ongoing checks every few minutes with alerts when something breaks, use uptime monitoring instead.

Is my question or the site I enter stored?

The question is stored so we can see what people are asking and improve our guides; the diagnostic results are not. We do not share the site you check with anyone.

Related guides

MonitoringHow to Reduce False Alerts in Website Monitoring Without GapsStop false uptime alerts without losing real ones: confirmation checks, retries, timeouts, WAF blocks, keyword checks, maintenance windows and slow alerts.9 min readMonitoringWhat 99.9% Uptime Really Means in Minutes, Hours and Days per YearA clear guide to uptime percentages with an exact downtime table for 99% to 99.999%, plus SLA vs SLO, measured vs reported uptime and check frequency.8 min read

Want one specific check instead? Is it down · SSL checker · DNS checker · Security headers