Skip to content

Use a custom domain

By default a status page lives at https://statuspage.siteqwality.com/<account-id>/<page-id>. A custom domain such as status.yourcompany.com serves it on your own subdomain, one per page, with a TLS certificate Site Qwality provisions through AWS Certificate Manager (ACM).

Each custom domain is a paid status page extra. See plan limits.

1. Register the custom domain in Site Qwality

Section titled “1. Register the custom domain in Site Qwality”
  1. Open the status page in the dashboard and go to its Custom Domain tab.

  2. Under Domain, enter your subdomain, e.g. status.example.com, and click Set Up Domain. An apex domain (example.com with no subdomain) can’t take a CNAME record, so it isn’t supported.

  3. The tab shows Pending DNS Validation with the two CNAME records to add at your DNS provider.

Or through the API, with an API key exported as SITEQWALITY_API_KEY and the page’s id as STATUS_PAGE_ID:

Terminal window
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"
},
...
}

In your DNS provider (Cloudflare, Route53, NS1, etc.) add a traffic CNAME that points your subdomain at Site Qwality, and an ACM validation CNAME that proves to AWS you control the domain so it can issue the certificate:

Record typeNameValueTTL
CNAMEstatus (i.e. status.example.com)Record 1’s value on the tab (cname_target in the API)300 (or auto)
CNAMERecord 2’s name (acm_validation.name), e.g. _xyz.statusRecord 2’s value (acm_validation.value), e.g. _xyz.acm-validations.aws300

Keep both records for as long as you use the domain: the certificate renews only while the validation record is in place.

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.

The Custom Domain tab updates on its own. Through the API, poll:

Terminal window
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.

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 (https://statuspage.siteqwality.com/<account-id>/<page-id>) still works as a fallback.

Your domain also serves the page’s feeds, badge and embed script. Any other path on it answers with a short “Page not found” page that links back to your status page.

Once the domain is live, Site Qwality checks every 6 hours that your hostname still points at the cname_target and that the certificate is issued and renewing. The Custom Domain tab shows when it was last checked and when the certificate expires. If something is wrong it shows Needs attention with what to fix, such as a CNAME that was removed or now points elsewhere, or a renewal waiting on the validation record. The API returns the same in the health field.

With the page white-labeled, subscriber email carries your page’s name, and it can also come from your domain, as notifications@status.example.com, signed for it. Add the third, optional CNAME the Custom Domain tab shows as Record 3 (optional): Email from your domain. Once the domain is live, Site Qwality checks the record every 15 minutes until it is verified, then every 6 hours. The API returns the same in the sender field.

Until the record is verified, or if it is later removed, subscriber email goes out from Site Qwality’s address. Without white-label it always does.

On the Custom Domain tab, click Remove Domain. Through the API:

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

The domain stops serving at once. Deleting the status page removes its custom domain the same way. In either case, delete the CNAME records you added from your DNS so they do not dangle.