# Site Health Audit - HTTPS, cert expiry, mobile viewport (`sterlingworks/site-health-audit`) Actor

Feed it a list of domains; get back per-domain HTTPS status, certificate expiry (days left), self-signed/mismatch/expired flags, HTTP status, mobile viewport tag, page title, response time and a 0-100 health score.

- **URL**: https://apify.com/sterlingworks/site-health-audit.md
- **Developed by:** [Emily Tomson](https://apify.com/sterlingworks) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 domain auditeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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

```json
{
  "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)

```json
{"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.

# Actor input Schema

## `domains` (type: `array`):

Domains or URLs to audit, one per line (example.com or https://example.com/path).

## `timeout` (type: `integer`):

Per-request timeout.

## `concurrency` (type: `integer`):

Parallel checks.

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "expired.badssl.com",
    "self-signed.badssl.com"
  ],
  "timeout": 10,
  "concurrency": 20
}
```

# Actor output Schema

## `overview` (type: `string`):

Every audited domain with its score and issue flags.

## `results` (type: `string`):

Full dataset, one JSON object per domain.

## `csv` (type: `string`):

Same records as CSV, ready for Excel, Google Sheets or a CRM import.

## `certificates` (type: `string`):

Host, TLS status, days left, expiry date and issuer only.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "example.com",
        "expired.badssl.com",
        "self-signed.badssl.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sterlingworks/site-health-audit").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "domains": [
        "example.com",
        "expired.badssl.com",
        "self-signed.badssl.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("sterlingworks/site-health-audit").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "example.com",
    "expired.badssl.com",
    "self-signed.badssl.com"
  ]
}' |
apify call sterlingworks/site-health-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sterlingworks/site-health-audit"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/cPaSd8tfW0Fk2I2nn/builds/RIJKTR5RlfB7YkiNW/openapi.json