Custom Domains

Connect a hostname like status.example.com to a status page so it runs entirely under your own brand. A hostname can be bound to exactly one status page, and the certificate is issued automatically once the domain is verified and active.

How it works

A custom domain moves through three states:

Pending — added, waiting for DNS verification.
Verified — the TXT record was found; ready to activate.
Active — the page is served on the hostname over HTTPS.

Add hostname  →  Add TXT record  →  Verify  →  Activate  →  Point CNAME
   (pending)        (your DNS)      (verified)   (active)     (traffic)

Step 1 — Add the hostname

In the app: Dashboard → Status Pages → (page) → Custom Domain → Add, enter status.example.com. Via the API: Add Custom Domain.

Uptimeify returns a TXT verification record:

TXT name: _uptimeify-verify.status.example.com
TXT value: the token shown in the app / API response

Step 2 — Add the TXT record

Create the TXT record in your DNS provider exactly as shown. Keep it in place — it is also re-checked over time.

DNS changes can take anywhere from a few minutes to a few hours to propagate. If verification fails immediately, wait and retry.

Step 3 — Verify

Click Verify (or call Verify Status Page Domain). Uptimeify looks up the TXT record and checks the token matches. On success the domain becomes Verified.

Step 4 — Activate

Click Activate (or call Activate Status Page Domain). The domain becomes Active and a TLS certificate is provisioned automatically (on-demand HTTPS) — no certificate upload required.

Step 5 — Point traffic to Uptimeify

Finally, point the hostname at Uptimeify so visitors actually reach the page — add the CNAME shown in the app for status.example.com. Once DNS resolves, https://status.example.com/ serves your status page.

Keep both records in place: the TXT record (used for ongoing verification) and the CNAME (routes visitor traffic). Removing the TXT record can cause the domain to fail re-verification.

Removing a domain

Remove the binding in the app or via Remove Custom Domain. The status page stays reachable on its /status/<slug> and /status/<id> URLs.

Troubleshooting

"TXT verification failed (token not found)"

Confirm the TXT name is exactly _uptimeify-verify.<your-hostname>.
Confirm the TXT value matches the token from Uptimeify (no extra quotes or spaces).
Give DNS more time to propagate, then verify again.
Check you didn't add the record to the wrong zone (e.g. apex vs subdomain).

The page doesn't load on my domain

Make sure the domain is Active, not just Verified.
Confirm the CNAME points to the target shown in the app.
The first request after activation may be slightly slower while the certificate is issued.