Docs

Custom domains

Serve your status page from your own hostname — status.yourcompany.com instead of /s/your-page. Available on Starter and above. The whole setup is two DNS records and takes about five minutes.

Who does what

You add two DNS records for your domain, then click Check DNS. That’s the whole job — it’s self-serve, and you don’t need to contact us.

We handle everything else automatically: serving the page on your hostname, issuing and renewing the HTTPS certificate, and keeping the page online. Allow up to an hour after verification for the certificate to go live; everything after that is hands-off.

Where the records go (not your servers)

The two records are added wherever your domain’s DNS is managed — Cloudflare, GoDaddy, Route 53, Namecheap, your registrar’s DNS panel. That is the only thing that changes.

Nothing is installed or configured on the servers that run your product. If your app runs on your own hardware, a VPS, or Kubernetes, none of that is touched: status.yourcompany.com simply points at IsItStillUp’s infrastructure, and we serve the page from there. That separation is the point — the status page stays up precisely because it does not run on the infrastructure it reports on.

The three steps

1. In Dashboard → Settings → Custom domain, enter your hostname (a subdomain like status.yourcompany.com works best) and click Connect domain. The page then shows your two records, with copy buttons:

CNAME  status.yourcompany.com          -> www.isitstillup.com
TXT    _beacon-verify.status.yourcompany.com -> beacon-verify-<your token>

2. Add both at your DNS provider. On Cloudflare, set the CNAME to DNS only (grey cloud), not Proxied.

3. Back in Settings, click Check DNS. The TXT record proves you control the domain; once it verifies, your page serves from the new hostname and https:// follows automatically within the hour. Your /s/ URL keeps working too.

Troubleshooting

“TXT record not found” right after adding it — DNS caches an earlier “no such record” answer for up to an hour. Wait a little and click Check DNS again; adding the TXT before the CNAME avoids this entirely.

Apex domains (yourcompany.com with no subdomain) can’t carry a CNAME per the DNS spec. Use a subdomain like status. — or, if your DNS provider supports ALIAS/ANAME flattening, point the apex at the same target.

Stuck? Email support@isitstillup.com — include your domain and we’ll check it from our side.