# Status page on your own domain

Put a status page on status.yourcompany.com, with the DNS records, verification and HTTPS.


From the Starter plan, a status page can live on your own domain, such as `status.example.com`. Use a
subdomain: the status page should stay up when your main site doesn't, so keep it off the servers it
reports on.

## 1. Add the domain

Open the status page in **Status pages**, enter `status.example.com` under **Your own domain**, and save.

## 2. Prove it's yours

The page now shows a TXT record. Add it at your DNS provider:

| Type | Name | Value |
|---|---|---|
| TXT | `_pulsefast.status.example.com` | `pulsefast-verify=…` (copy it from the page) |

Some providers want only the part before your domain in **Name** (`_pulsefast.status`). Then click
**Verify domain**. DNS changes can take a few minutes to appear.

Verification stops anyone else from claiming your domain. If the domain was used on another Pulsefast
status page before, the latest proof wins.

## 3. Point it at Pulsefast

| Type | Name | Value |
|---|---|---|
| CNAME | `status` | `pulsefast.io` |

**Cloudflare:** set the record to **DNS only** (grey cloud), at least until the certificate is issued.

## 4. HTTPS

A certificate is issued automatically on the first visit, which can take a few seconds. Open
`https://status.example.com` to check. Renewals are automatic.

## If it doesn't work

- **"We couldn't find the TXT record":** check the name (some providers add your domain twice), and
  wait a few minutes. `dig TXT _pulsefast.status.example.com` shows what the world sees.
- **The page doesn't load:** check the CNAME with `dig CNAME status.example.com`, and that the domain
  was verified (the status page's settings say so).
- **After a downgrade** to a plan without custom domains, the page is still served at its
  `pulsefast.io/s/…` address, but not on your domain.