Incidentsintermediate

Connect a custom domain for the status page

Add a domain like status.yourcompany.com so visitors see your status page at your own URL instead of the default tenant slug.

May 11, 202610 min read

Connect a custom domain for the status page

Customers reaching https://status.yourcompany.com looks far more trustworthy than https://your-tenant.atender.dev/incidents/your-slug. Custom domains make your status page feel like an extension of your product. This article walks through adding one.

Before you start

  • You need access to manage DNS records on the domain you’ll use (typically a subdomain like status.yourcompany.com).
  • Pick a subdomain. Standard choices are status, health, or uptime. Apex domains (yourcompany.com) don’t work as well for status pages — keep it on a subdomain.
  • An Admin or Owner role on the Atender tenant.

Steps

1. Open the Domains tab

Go to Settings → Incidents Settings → Domains. You see the list of currently-connected domains (empty initially).

2. Add the domain

Click Add Custom Domain in the top-right. Enter the domain you want to use, e.g., status.yourcompany.com. Click Add Domain.

The domain appears in the list. At this point Atender knows about it — but DNS isn’t pointing at us yet, so the domain doesn’t serve traffic.

3. Update DNS

Atender shows you the DNS target your subdomain needs to point at. The pattern is a CNAME to Atender’s incidents host:

  • CNAMEstatus (or your chosen prefix) — the target shown in the UI

Go to your DNS provider (Cloudflare, Route 53, GoDaddy, your registrar’s panel) and create the CNAME record exactly as shown. If you already have a record at that subdomain, replace it.

4. Wait for DNS to propagate

Most DNS providers propagate in 5–15 minutes. Some take up to 24 hours. You can check propagation by running dig CNAME status.yourcompany.com (or use a web-based DNS lookup tool). Once the lookup returns Atender’s target, you’re set.

5. Verify in Atender

Refresh the Domains tab. Your domain should now show as connected. Open https://status.yourcompany.com in a browser — the status page loads, served from your domain.

What gets served from the custom domain

The full public status page — incidents, components, history, subscriber dialog — is served from your domain. The embed widget URLs (script and iframe) generated on the Embed tab also use the default tenant URL; you can manually replace the host in those snippets with your custom domain if you want the embedded widget to load from your own domain too.

HTTPS

Atender automatically provisions and renews a TLS certificate for the connected domain. You don’t need to bring your own. The first certificate may take a few minutes after DNS resolves correctly.

Multiple domains

You can connect more than one domain — for example, status.yourcompany.com and status.yourbrand.com both pointing at the same status page. Each one needs its own CNAME and shows up as a separate entry in the Domains tab.

Verify it worked

  1. dig CNAME status.yourcompany.com returns Atender’s target.
  2. https://status.yourcompany.com loads the page (with HTTPS, no certificate warnings).
  3. The page content matches what’s at https://<your-tenant>.atender.dev/incidents/<your-slug>.

Removing a custom domain

Click the trash icon next to the domain in the Domains tab. Atender stops serving traffic for that domain immediately. Your DNS record at the registrar will keep pointing to nothing until you update it — clean up the CNAME on your side to avoid a stranded record.

Troubleshooting

  • Symptom: “Domain not yet active” persists. Fix: DNS hasn’t propagated. Use dig to verify the CNAME resolves to Atender’s target. If your registrar shows the record correctly but dig still returns the old value, wait — TTL hasn’t expired yet.
  • Symptom: Browser shows a certificate error. Fix: Atender provisions the certificate after DNS resolves. Give it 5–10 minutes after the DNS lookup starts working. If it persists, refresh the Domains tab — there may be an error state shown there.
  • Symptom: Status page loads but with the wrong tenant’s content. Fix: Confirm the CNAME target matches what’s shown in your tenant’s Domains tab — not a target you remember from another tenant. Each tenant gets a distinct host target.

See also

Tags

How To

See Atender in action

Book a personalized demo and see how AI-powered customer service with expert humans can transform your support operation.