Use your own domain

A status page can live on your own domain — status.example.com rather than our address. Worth doing: during an outage, people trust a page on your domain and hesitate over one that is not.

Set it up

1. Enter the domain on the status page's settings — a subdomain you control, like status.example.com.
2. At your DNS provider, create a CNAME record pointing it at pages.uptimecraft.com.
3. Come back and press Check DNS.
4. Visit the domain. The certificate is issued on the first visit, so the very first load may take a few seconds.

When it does not work

"DNS does not point here yet." Usually propagation — give it a few minutes and check again. Confirm with dig status.example.com CNAME or nslookup status.example.com that the answer really is pages.uptimecraft.com.

Proxied DNS (Cloudflare's orange cloud). The most common cause by far. With proxying on, the CNAME resolves to Cloudflare rather than to us, we cannot see your record, and the certificate cannot be issued. Set the record to DNS only (grey cloud).

A CAA record on your domain. If you publish CAA records, they tell certificate authorities who may issue for you. One that does not include the authority we use will block issuance silently. Either add it or remove the CAA record for that subdomain.

An apex domain. example.com itself usually cannot be a CNAME. Use a subdomain; status. is the convention and what people will guess.

An existing record. A subdomain that already has an A or AAAA record cannot also be a CNAME. Remove the old one first.

Afterwards

The certificate renews on its own. If you ever remove the CNAME, the page stops answering on your domain and remains reachable at its original address — so pointing the DNS away is a safe way to undo this.