- Open the status pageGo to Status pages and open the page you want to put on your domain.
- Add the hostnameUnder Custom domain, enter a subdomain you control, such as status.example.com, and choose "Add domain".
- Create the TXT recordAt your DNS provider, create the Ownership TXT record exactly as shown in the table.
- Create the CNAME recordCreate the Routing CNAME record for your hostname pointing to the value shown. On Cloudflare, set it to DNS only.
- Check DNSChoose "Check DNS now". When ownership and routing are verified, the HTTPS certificate is issued automatically within a few minutes.
On Starter and Team you can serve a status page at your own subdomain, such as status.example.com. You prove ownership with a TXT record, route traffic with a CNAME record, and Uptime Tracker issues the HTTPS certificate automatically.
Add the domain
Open the status page and find the Custom domain section. Enter a Hostname, a subdomain you control, and choose Add domain. Use a subdomain rather than your bare domain, because a CNAME record cannot sit at the root of a zone with most DNS providers.
Create the two DNS records
The page then shows a table of DNS records to create. Copy the values exactly from that table:
| Purpose | Type | Name | Value |
|---|---|---|---|
| Ownership | TXT | _monitoring-verify.status.example.com | monitoring-verify=… (your token) |
| Routing | CNAME | status.example.com | The target shown on the page |
Some DNS providers add your domain to the name automatically. In that case enter only _monitoring-verify.status and status as the names.
If your DNS is on Cloudflare, set the CNAME record to DNS only (grey cloud), not proxied. Otherwise the routing check and certificate issuance cannot complete.
Verify
Choose Check DNS now. DNS changes can take from a few minutes to a few hours to propagate, depending on your provider and the record's TTL. The section shows the state of each part:
- Ownership: verified once the TXT record is found.
- Routing: verified once the CNAME points to the right target.
- Certificate: issued automatically within a few minutes after both are verified.
When everything is ready, the domain shows as active and the page lists Also served at your hostname. The original /status/<address> link keeps working too.
Keep the TXT record
Leave both records in place after verification. The TXT record proves ownership and the CNAME routes traffic; removing either can take the custom domain offline.
Remove or change the domain
Choose Unbind domain. The hostname stops serving the status page immediately. To use it again, you must add and verify it again. Each status page can have one custom domain at a time.
Troubleshooting
- The last check time and any error are shown under the domain. Read the error first; it usually names the missing or wrong record.
- Check the records with a DNS lookup tool or
dig TXT _monitoring-verify.status.example.comanddig CNAME status.example.com. - Your own application's hostname cannot be used.
Frequently asked questions
Which plan supports a custom status page domain?
Starter and Team. Free status pages use the uptimetracker.live/status/
link.Do I need to buy an SSL certificate?
No. Once the TXT and CNAME records are verified, the HTTPS certificate is issued automatically.
My DNS is on Cloudflare. What should I set?
Set the CNAME record to DNS only (grey cloud), not proxied, so verification and certificate issuance can complete.
Can I use my root domain?
Use a subdomain such as status.example.com. Most DNS providers do not allow a CNAME at the root of a domain.
