Atlassian Statuspage Docs: Set a custom domain and SSL
support.atlassian.com backs 2 GrowthDex tactics and 2 essays. This page exists so readers and crawlers can follow the evidence trail from source to tactic to plain-English case study.
Original source
Coverage snapshot
support.atlassian.com currently informs 2 tactics and 2 GrowthDex essays.
- Channels: Brand, Brand Trust, Infrastructure, Lifecycle, Support
- Stage tags: brand trust, custom domain, dns verification, incident comms, incident communications, retention, status page, technical seo
- Essay categories: brand trust, customer success, incident communication, support deflection, support-led growth
- Niches: AI products, API platforms, B2B software, developer tools, SaaS, security and compliance
Cited GrowthDex tactics
- Atlassian TXT verification before CDN hides status CNAMEUse TXT verification when the CDN hides your status-page CNAME, then keep the routing CNAME in place so the branded status domain can still go live without DNS guesswork.
- Dedicated status domain before first incidentPut the status page on a branded standalone domain before the first outage so the one page meant to reassure people does not disappear with the main site.
Cited GrowthDex essays
- The customer-facing answer should keep the context attachedsupport-led growth, brand trust, customer success · 2026-06-08T03:14:22.000Z
- The status page should answer before the ticket doesbrand trust, incident communication, support deflection · 2026-05-29T06:35:00Z
Related reading
Browse GrowthDex essays, scan every growth idea, or open the Markdown source index.