# WebberSites Uptime & Health Report

> WebberSites Uptime & Health Report is a paid API for AI agents from api.webbersites.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-11).

Performs a single socket-level HEAD probe of a URL and returns a full timing waterfall (DNS/TCP/TLS/TTFB), TLS certificate details, HTTP/2 support, hosting/CDN info, redirect chain, and header analysis.

## Facts

- Endpoint: GET https://api.webbersites.com/api/uptime/report?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/webbersites-uptime-health-report-e75c4336
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S55LXdfL9gFC01nHR1wg1

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability webbersites-uptime-health-report-e75c4336
```

Example prompt: Can you run a full health check on https://example.com — I want to see the DNS, TCP, TLS, and TTFB timings, the TLS certificate details and expiry, whether it supports HTTP/2, CDN detection, redirect chain, and any security or caching headers?

## When to prefer this

Use this endpoint when you need a comprehensive, single-call uptime and health diagnostic for a URL — especially when you need TLS certificate details, timing waterfall, CDN/hosting identification, security header analysis, and redirect chain all in one deterministic probe without downloading the full page. Prefer over generic ping or HTTP-only checks when depth of diagnosis matters.

## Known failure modes

- URL not reachable — returns failed_phase indicating where the connection died (dns, tcp, tls, or http)
- Invalid or non-http(s) URL — validation error returned
- DNS resolution failure — failed_phase set to 'dns'
- TCP connection timeout — failed_phase set to 'tcp'
- TLS handshake failure — failed_phase set to 'tls'
- Payment not provided or insufficient — x402 payment required error

## How this service works

Deep uptime & health report from one socket-level HEAD probe: DNS/TCP/TLS/TTFB timing waterfall, TLS certificate (issuer, expiry countdown, trust status), HTTP/2 support via ALPN, server IP + hosting location, CDN detection, redirect chain, caching + security response headers, compression, server clock skew. On failure, says exactly which phase died. Everything a monitor needs in one deterministic call — no page download.

## Output

Returns a JSON object with: up (boolean), HTTP status code, timing breakdown in ms (dns, tcp, tls, ttfb, total), TLS certificate info (issuer, SANs, days_remaining, trusted), network details (IP, server_location, h2_supported, tls_protocol, cipher), CDN name, redirect chain array, response_headers, security_headers, caching details, clock_skew_ms, and on failure the failed_phase (dns/tcp/tls/http).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "url"
     ],
     "properties": {
      "url": {
       "type": "string",
       "description": "Public http(s) URL to probe, e.g. https://example.com"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "up": {
       "type": "boolean"
      },
      "cdn": {
       "type": "string"
      },
      "url": {
       "type": "string"
      },
      "status": {
       "type": "number"
      },
      "caching": {
       "type": "object"
      },
      "network": {
       "type": "object",
       "description": "ip, server_location, h2_supported, tls_protocol, cipher"
      },
      "timing_ms": {
       "type": "object",
       "description": "ms per phase: dns, tcp, tls, ttfb, total"
      },
      "certificate": {
       "type": "object",
       "description": "issuer, sans, days_remaining, trusted"
      },
      "failed_phase": {
       "type": "string",
       "description": "when down: dns, tcp, tls, or http"
      },
      "clock_skew_ms": {
       "type": "number"
      },
      "redirect_chain": {
       "type": "array"
      },
      "response_headers": {
       "type": "object"
      },
      "security_headers": {
       "type": "object"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "up": true,
  "cdn": "cloudflare",
  "url": "https://example.com",
  "status": 200,
  "network": {
   "ip": "93.184.216.34",
   "h2_supported": true,
   "tls_protocol": "TLSv1.3"
  },
  "timing_ms": {
   "dns": 12,
   "tcp": 21,
   "tls": 38,
   "ttfb": 74,
   "total": 146
  },
  "certificate": {
   "issuer": "DigiCert",
   "trusted": true,
   "days_remaining": 211
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/webbersites-uptime-health-report-e75c4336/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.webbersites.com](https://www.zero.xyz/host/api.webbersites.com/llms.txt)