Use a custom domain

By default a status page lives at <page-id>.siteqwality.com. Adding a custom domain — typically status.yourcompany.com — takes a few minutes plus DNS propagation time.

SiteQwality provisions the TLS certificate via AWS Certificate Manager (ACM) and serves the page from the same edge as the default URL. There’s no extra runtime cost or proxy hop.

What you’ll add to DNS

You’ll create two CNAME records:

A traffic CNAME — your subdomain points at SiteQwality’s edge.
An ACM validation CNAME — proves to AWS you control the domain so it can issue the cert.

Both values come from the API response in step 1 below.

1. Register the custom domain in SiteQwality

Open the status page in the dashboard, then Settings → Custom domain → Add domain.
Enter your subdomain — e.g. status.example.com. Save.
The page reloads with two CNAME records to add to your DNS provider, plus a status badge that starts at pending_validation.

Or via the API:

curl -X POST https://api.siteqwality.com/status_page/$STATUS_PAGE_ID/custom_domain \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "domain": "status.example.com" }'

The response includes:

{
  "status_page_id": "abc123",
  "domain": "status.example.com",
  "status": "pending_validation",
  "cname_target": "abc123.custom.siteqwality.com",
  "acm_validation": {
    "name": "_xyz.status.example.com",
    "value": "_xyz.acm-validations.aws"
  },
  ...
}

2. Add both CNAME records

In your DNS provider (Cloudflare, Route53, NS1, etc.) add:

Record type	Name	Value	TTL
`CNAME`	`status` (i.e. `status.example.com`)	`<cname_target from step 1>`	`300` (or auto)
`CNAME`	`_xyz.status` (the `acm_validation.name`)	`_xyz.acm-validations.aws` (the `acm_validation.value`)	`300`

3. Wait for validation

ACM polls your DNS for the validation record every ~5 minutes. The status field progresses through:

pending_validation — DNS records not yet seen.
provisioning — validation passed, certificate being issued.
active — fully live; your domain serves the status page.
failed — something went wrong; check failure_reason in the API response.

Refresh the dashboard or poll:

curl https://api.siteqwality.com/status_page/$STATUS_PAGE_ID/custom_domain \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY"

Total time is usually 5–15 minutes once both DNS records are in place.

4. Verify

Open https://status.example.com in a fresh browser. You should see:

A valid TLS certificate (no warnings).
Your branded status page.
The default URL (<page-id>.siteqwality.com) still works as a fallback.

Removing a custom domain

curl -X DELETE https://api.siteqwality.com/status_page/$STATUS_PAGE_ID/custom_domain \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY"

Or use the Remove button in the dashboard. Removing the custom domain immediately stops serving it; you should also delete the two CNAME records from your DNS to avoid a dangling pointer at SiteQwality’s edge.

Notes

Only one custom domain per status page.
Apex domains (example.com with no subdomain) aren’t supported because of the CNAME-at-apex restriction in DNS. Use a subdomain like status or health.
The certificate auto-renews. If renewal ever fails, the dashboard surfaces a warning with the failure reason.