Custom domain
A Custom domain serves your Status page at a name of your own, such as status.acme.com, in place of its address on our domain, such as acme.uupstatus.com.
The name must be a subdomain of a domain you own: status.acme.com, never acme.com itself. Custom domains come with every paid plan. Only owners and admins can connect one.
Connecting a name
Section titled “Connecting a name”- In the sidebar, open Status page.
- Under Custom domain, type the name and press Connect.
- At your DNS provider, add the two records the card shows. For
status.acme.comthey are:
| Type | Name | Value |
|---|---|---|
TXT | _uup.status.acme.com | Your own token, shown on the card |
CNAME | status.acme.com | cname.uupstatus.com |
The TXT record proves the name is yours. The CNAME record points the name at uup. Add both at once: we look for the CNAME record as soon as the TXT record is found.
The card then shows Waiting for TXT, then Waiting for CNAME, then Live. We look for the records on our own, and Check now looks at once. A change at your DNS provider can take a while to show.
Once both records are in place, we issue an HTTPS certificate for the name, and the page is served at it. The page’s address on our domain then forwards to the Custom domain. Status badges you already pasted keep working at either address.
We read the TXT record once. The CNAME record must stay for as long as the name is connected.
Notes for DNS providers
Section titled “Notes for DNS providers”- The name field. Many providers add your domain to the name you type. If yours does, type only the part before your domain:
_uup.statusfor the TXT record andstatusfor the CNAME record. - Cloudflare. Set the CNAME record’s Proxy status to DNS only. A proxied record answers with Cloudflare’s own addresses, which hides where the name points, so the card says the name is behind a proxy. For the same reason, turn off CNAME flattening for this record if it is on.
- Route 53. Create a CNAME record with Alias off. In Record name, type only the part before your domain, which Route 53 shows beside the field.
- Other proxies. Any service that answers for the name with its own addresses hides the CNAME record in the same way. Point the name straight at us.
- Other records at the name. A name that has a CNAME record can have no other records. Remove any other record at
status.acme.comfirst.
What the card shows
Section titled “What the card shows”| On the card | What it means |
|---|---|
| Waiting for TXT | The TXT record is not found yet, or it holds another value. Set it to the value the card shows. |
| Waiting for CNAME | The TXT record is found, so the name is yours. The CNAME record is not found yet, points somewhere else, or is behind a proxy. |
| Live | The page is served at the name, over HTTPS. |
| CNAME missing | The name was Live, and its CNAME record is gone. The page still works at the name for now. Put the record back to keep the name. |
| CNAME points elsewhere | The name was Live, and its CNAME record now points somewhere else. Point it at the value the card shows. |
| Behind a proxy | The name was Live, and its CNAME record is now behind a proxy. Set it to DNS only to keep the name. |
| Claimed elsewhere | The name is connected to another account’s page. A name can be connected to one page only. Press Remove to connect another name. |
| Not on your plan | Your plan no longer covers a Custom domain. The page is served at its address on our domain again. The name and its records are kept, so a paid plan brings the name back. |
When a name is released
Section titled “When a name is released”A released name is no longer connected to your page, and the page is served at its address on our domain again. A name is released when:
- you press Remove. To connect the name again later, you add its records again.
- you connect another name in its place.
- its records are not both found within 7 days of pressing Connect.
- after it was Live, it stops pointing at us for 30 days in a row. Until then the card shows the day the name will be released.
When a name is released for either of the last two reasons, the card says so and why.
A DNS lookup that fails on our side changes nothing, so it can never release a name.
After a name leaves us
Section titled “After a name leaves us”A browser that opened your page at the Custom domain keeps using HTTPS for that name for 365 days. Wherever you point the name next, serve it over HTTPS.