Skip to Content
Uptimeify Docs
Status pages

Custom Domains

Connect a hostname like status.deinkunde.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:

  1. Pending: added, waiting for DNS verification.
  2. Verified: the TXT record was found; ready to activate.
  3. 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.deinkunde.com. Via the API: Add Custom Domain.

Uptimeify returns a TXT verification record:

  • TXT name: _verify-status.status.deinkunde.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.

Domains verified before 13 May 2026 use the older record name _uptimeify-verify.<your-hostname>. That record stays valid and keeps verifying; nothing to change. New domains always use the name shown above.

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.deinkunde.com. Once DNS resolves, https://status.deinkunde.com/ serves your status page.

Keep both records in place: the TXT record (used for ongoing verification) and the CNAME (routes visitor traffic). If the TXT record disappears the weekly re-check reports it and we get in touch; your domain is never switched off automatically.

Apex domains (example.com without a subdomain)

A CNAME is not allowed on the apex of a zone, so deinkunde.com itself cannot simply point at Uptimeify like status.deinkunde.com can. Two ways work:

  • Your DNS provider supports CNAME flattening, ALIAS or ANAME: create that record type on the apex with the same target the app shows for the CNAME. Examples: Cloudflare (CNAME flattening, applied automatically to a CNAME on the apex), Bunny DNS (CNAME flattening), Amazon Route 53 (alias record), DNSimple (ALIAS record). The TXT record from step 2 stays as it is.
  • Your provider offers none of these: use a subdomain such as www.deinkunde.com or status.deinkunde.com as the custom domain and set up a redirect from the apex to it at your registrar or DNS provider.

Do not point the apex at our IP addresses with A or AAAA records. Status pages are served from several frontends, and the addresses behind the CNAME target change when traffic fails over from one frontend to another. A hard-coded IP address does not follow that failover, so your page could go offline exactly when it is needed most.

When changes show up

Saved changes to the page (name, design, components, incidents) are live on the next reload, on your own domain as on /status/<slug>: the status page HTML is never cached (Cache-Control: no-store). Two things take a little longer on your own domain:

  • Publishing, unpublishing and a new address take up to 30 seconds, because each server remembers which page a hostname belongs to for that long.
  • Badge, widget and feeds may be cached for up to 60 seconds.

An unpublished page answers with HTTP 404 on your own domain too, without a redirect to the sign-in page.

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 _verify-status.<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.

On this page