Website Uptime Monitor for SSL and Content

Turn a list of website or API URLs into one health record per endpoint for operations teams, developers, agencies, SaaS teams, and AI agents. Each row can include availability, HTTP status, response time, SSL certificate details, content-match evidence, redirects, performance grade, health score, selected headers, diagnostic context, final URL, and collection time.

Best fit for this Actor

• Choose this Actor for scheduled or on-demand health checks across public websites, APIs, landing pages, and status endpoints.
• Add a keyword or regular expression when a successful response must also contain expected page content.
• Use expected status codes and HTTP method controls for owned APIs with a specific health contract.
• Pair this Actor with the Broken Link Checker when priority URLs need a crawl, sitemap, or link-inventory audit.

From a launch checklist to a health brief

An operations lead starts with production URLs and an expected page phrase. The Actor checks each endpoint, follows configured redirects, inspects SSL details, verifies content, and records timing in a consistent dataset. The lead then sorts by health score and response time, opens the HTML report for review, and schedules the same input so each observation remains comparable through url, finalUrl, and checkedAt.

Quick start input

{
  "startUrls": [
    { "url": "https://example.com" },
    { "url": "https://api.example.com/health" }
  ],
  "keyword": "Welcome",
  "expectedStatusCodes": [200],
  "checkSsl": true,
  "followRedirects": true
}

The Actor accepts request-list sources through startUrls. Keep the HTTP method aligned with an endpoint you own when using methods that can change server state.

Input reference

Field	Type	What it controls
startUrls	array	Website, landing-page, API, or status URLs to monitor.
keyword	string	Case-insensitive page-content check.
regex	string	Case-insensitive JavaScript pattern for flexible content validation.
expectedStatusCodes	array	Explicit HTTP codes treated as healthy for the workflow.
method	string	HTTP method used for each endpoint check.
checkSsl	boolean	Includes certificate issuer and expiry observations for HTTPS URLs.
followRedirects, maxRedirects	boolean, integer	Redirect behavior and hop cap.
timeoutMs, maxConcurrency	integer	Request timing and parallelism controls.
useApifyProxy, proxyConfiguration	boolean, object	Optional Apify proxy routing.

What data you receive

One dataset item represents one endpoint observation. The Actor also creates a summary, an HTML report, and a run-configuration record in the default key-value store.

Field group	Useful fields
Health	isUp, healthScore, performanceGrade
HTTP	statusCode, statusText, responseTimeMs, headers
SSL and content	ssl, contentMatch
Routing	url, finalUrl, redirects
Diagnostic context	diagnostic, durationMs, checkedAt

{
  "url": "https://example.com",
  "isUp": true,
  "healthScore": 98,
  "performanceGrade": "A",
  "statusCode": 200,
  "statusText": "OK",
  "responseTimeMs": 240,
  "ssl": {
    "valid": true,
    "issuer": "Example Certificate Authority",
    "daysRemaining": 70
  },
  "contentMatch": {
    "checked": true,
    "matched": true,
    "pattern": "Welcome"
  },
  "redirects": [],
  "finalUrl": "https://example.com/",
  "diagnostic": null,
  "checkedAt": "2026-06-02T09:00:00.000Z",
  "durationMs": 260
}

Use through the API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~website-uptime-monitor/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "startUrls": [{"url": "https://example.com"}],
    "keyword": "Welcome",
    "expectedStatusCodes": [200],
    "checkSsl": true
  }'

Read the default dataset for per-URL observations. Use the Actor output links to retrieve the summary, HTML report, and recorded settings.

Use with AI agents through Apify MCP

Check these production URLs for HTTP health, response time, SSL details, expected content, redirects, final URL, health score, and collection time. Read the dataset and summary after completion, preserve each source URL, group observations by operational priority, and keep the scope within the supplied URL list.

For clean agent readback, provide canonical URLs, define the expected content or status contract, request the dataset fields needed for the decision, and preserve checkedAt with each observation. The supplied URL list keeps scope and cost transparent.

Connect the workflow

Use the Broken Link Checker when a health observation should continue into a broader site audit. Feed the selected URL into crawl mode for source-page discovery, or use list mode for a curated endpoint inventory.

Pricing

This Actor uses Pay per event plus Apify platform usage. Open the live Pricing tab for current event details, and use the URL list, concurrency settings, and Apify run cost controls to keep monitoring aligned with your budget.

Best results

• Use dedicated public health endpoints for API monitoring when they are available.
• Add a stable keyword or regular expression when rendered content matters to the outcome.
• Keep followRedirects enabled for end-user destination monitoring and preserve the redirect list for routing review.
• Schedule a consistent input when comparable observations over time support the operational decision.

Builder's note

I designed each endpoint row to combine transport, SSL, content, redirect, and timing evidence because I found that a single status code gives an incomplete operational picture. The health score is useful as a sorting aid, while the underlying fields remain present so people and agents can explain every priority decision.

Responsible use

Monitor endpoints you are authorized to assess, use considerate request settings, and follow applicable laws, site terms, and your organization's security and operations policies.