Custom domain for status pages
Serve your DomainCare status page on your own subdomain with automatic HTTPS — e.g. status.yourcompany.com.
Custom domain for status pages
Host your status page on your own subdomain instead of domaincare.io/status/<slug>. Visitors see your brand; TLS is provisioned automatically.
Why use a custom domain
- Trust during incidents. Users verify the hostname matches your company — a third-party URL looks suspicious during an outage.
- Link stability. If you switch status-page providers later, update one CNAME and every link keeps working.
- SEO. Search results for "yourcompany status" point to your domain.
- Branding. The status page is your most-visited surface during incidents.
Setup
1. Add the hostname
Go to Settings → Status pages → (your page) and find the Custom domain card. Enter your desired hostname — for example, status.yourcompany.com.
DomainCare generates two DNS records you need to create.
2. Create DNS records
Add both records at your DNS provider:
CNAME record
| Type | Name | Target |
|---|---|---|
| CNAME | status.yourcompany.com | cname.domaincare.io |
TXT record (ownership verification)
| Type | Name | Value |
|---|---|---|
| TXT | _domaincare.status.yourcompany.com | dc-verify=<token> |
The exact values are shown in the dashboard — use the copy buttons to avoid typos.
DNS propagation can take minutes to hours depending on your provider. Common fast providers (Cloudflare, Route 53, Vercel DNS) propagate in under five minutes.
3. Verify
Click Verify now in the dashboard. DomainCare checks that both records resolve correctly.
If verification fails, double-check:
- The CNAME target is exactly
cname.domaincare.io(no trailing dot in most providers). - The TXT record name starts with
_domaincare.— some providers auto-append your zone, so you may only need to enter_domaincare.statusas the name. - Your DNS provider isn't proxying the CNAME (Cloudflare users: set the CNAME to DNS only, not Proxied).
DomainCare also checks automatically every six hours. If both records aren't found within seven days, the custom domain configuration is removed.
4. Done
Once verified:
https://status.yourcompany.comserves your status page with a valid TLS certificate.domaincare.io/status/<slug>automatically redirects to your custom domain.- The Live at link in the dashboard updates to your custom domain.
- The
publicUrlfield in API responses reflects the custom domain.
Removing a custom domain
Click Remove custom domain in the dashboard. The page immediately reverts to domaincare.io/status/<slug>. The redirect stops and the TLS certificate is cleaned up.
API
Custom domains are also available via the public API:
POST /api/v1/status-pages/{id}/custom-domain— add a hostname or trigger verification.GET /api/v1/status-pages/{id}/custom-domain— check current status.DELETE /api/v1/status-pages/{id}/custom-domain— remove.
See the API documentation for details.
Limits
- One custom domain per status page.
- Subdomains only (e.g.
status.yourcompany.com). Apex domains (yourcompany.com) are not supported. - The hostname must not end in
.domaincare.io.
Troubleshooting
| Symptom | Fix |
|---|---|
| Verification stuck on "Pending" | Check DNS propagation. Try dig CNAME status.yourcompany.com and dig TXT _domaincare.status.yourcompany.com from your terminal. Both must resolve. |
| Browser shows certificate error | Vercel provisions the certificate after verification. Allow up to 10 minutes for the certificate to propagate. |
Old domaincare.io/status/<slug> URL still works without redirect | The redirect only applies when the custom domain is verified and the page is published. |