Site Health Audit

Give it a list of domains. Get back one clean, spreadsheet-ready row per domain: whether HTTPS works, exactly what is wrong with the certificate, how many days are left before it expires, whether the page actually loads, and whether the site is usable on a phone.

No crawling. No cleanup. Many domains in, one row out.

Views and exports

The Output tab ships three ready-made tables, and every one exports to CSV, Excel, JSON or XML in a click:

• Overview - host, score, issue flags, TLS status, days left, HTTP status, mobile, speed.
• Certificates - the expiry watchlist: status, days left, expiry date, issuer.
• Availability and mobile - what loads, how fast, final URL, viewport tag, server.

Every record carries every field, so the columns are stable even for domains that fail at DNS. Sort ascending by health_score to triage, or by cert_days_left to see what breaks next.

Output fields

field	meaning
reachable	DNS resolved and a page came back
https_ok / tls_status	OK, EXPIRING (under 15 days), EXPIRED, SELF_SIGNED, MISMATCH, NO_ISSUER, NO_HTTPS
cert_issuer, cert_expires, cert_days_left	read from the live certificate
http_status, final_url, redirects_to_https, response_ms, server	from the homepage fetch
has_viewport	mobile viewport meta tag present
title	page title
issues	flags: EXPIRED, SELF_SIGNED, MISMATCH, NO_HTTPS, NO_HTTPS_REDIRECT, NO_VIEWPORT, NO_TITLE, HTTP_404, SLOW, DNS_FAIL
health_score	0-100, weighted by severity (a dead certificate costs far more than a missing title)

Who it is for

• Agencies and web shops running 20-500 client sites. Run it weekly and never take the Saturday phone call about a browser security warning. A certificate expiring in 9 days shows up as cert_days_left: 9 long before a customer ever sees a warning.
• Anyone selling web services. Feed in a list of businesses, get back a sorted list of who has a visibly broken site, with the reason attached.
• Domain portfolio and due diligence. Hundreds of properties checked in one run.

Why this one

The store has single-domain certificate checkers, and large general-purpose crawlers. This is the piece in between: bulk domains in, one health row out. A 1,000-domain sweep finishes in about a minute.

Input

{
  "domains": ["example.com", "shop.example.org", "https://www.example.net/"],
  "timeout": 10,
  "concurrency": 20
}

URLs, bare hosts and www. prefixes are all accepted and normalised.

Sample output (real run)

{"host":"salons.greatclips.com","tls_status":"OK","cert_issuer":"Google Trust Services",
 "cert_days_left":80,"http_status":200,"has_viewport":true,"response_ms":99,
 "issues":[],"health_score":100}

{"host":"gratefulbeancoffee.com","tls_status":"OK","cert_days_left":30,"http_status":404,
 "has_viewport":false,"issues":["NO_VIEWPORT","NO_TITLE","HTTP_404"],"health_score":30}

{"host":"expired.badssl.com","tls_status":"EXPIRED","http_status":200,
 "issues":["EXPIRED"],"health_score":40}

Export the dataset as CSV, JSON or Excel, or pull it straight from the Apify API.

Notes

• 20 domains complete in about 8 seconds at the default concurrency.
• Certificates are read from a live TLS handshake, not from a cached third-party database.
• Unreachable hosts return reachable: false with DNS_FAIL or UNREACHABLE rather than failing the whole run.