Website Health Check

What it runs

1. 1
   SSL Certificate Chain

   Source: TLS handshake (full X.509 certificate chain from target server)

2. 2
   Email Deliverability Check

   Source: DNS protocol (SPF, DKIM, DMARC record verification) + blacklist check

3. 3
   Page Speed Test

   Source: Google PageSpeed Insights API (Lighthouse performance analysis)

The answer returns every step’s result, so your agent can show or check each one.

Inputs

How to call it

# Needs an API key. The whole check is charged once, at the listed price.
curl -X POST https://api.strale.io/v1/solutions/website-health/execute \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "inputs": {
      "domain": "google.com"
    },
    "max_price_cents": 40
  }'

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i -X POST https://api.strale.io/x402/v2/solutions/website-health \
  -H 'Content-Type: application/json' \
  -d '{
    "domain": "google.com"
  }'

The bundle’s published example input.

Limitations

• Validates chain to known root CAs — private/internal CAs will show as untrusted

  From step: SSL Certificate Chain

  What to do instead: If you use a private CA, compare the returned issuer fingerprint against your internal CA's known fingerprint

• SMTP verification may be blocked by some mail servers — a 'deliverable' result is not guaranteed delivery

  From step: Email Deliverability Check

  What to do instead: Treat SMTP-verified results as 'likely deliverable' and implement bounce handling in your email pipeline for definitive status

• Scores reflect a point-in-time test — site performance may vary throughout the day

  From step: Page Speed Test

  What to do instead: Schedule periodic tests (e.g., every 6 hours) and track the trend rather than relying on a single measurement

• Results measured from a single geographic location — actual user experience varies by region

  From step: Page Speed Test

  What to do instead: Run tests at multiple times and average the scores, or use the lab data breakdown to identify bottlenecks independent of location

• If Lighthouse cannot load the page because it is unavailable, blocks automated visitors, requires authentication or redirects in a loop, the call is refused. No score is returned and no charge is taken.

  From step: Page Speed Test

  What to do instead: Check the URL loads in a browser from a clean session, and that it is reachable without a login