# Dedicated status domain before first incident

> Put 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/dedicated-status-domain-before-first-incident/
- Source: [support.atlassian.com](https://support.atlassian.com/statuspage/docs/set-a-custom-domain-and-ssl/)
- GrowthDex source hub: [Atlassian Statuspage Docs: Set a custom domain and SSL](/sources/atlassian-statuspage-docs-set-a-custom-domain-and-ssl-support-atlassian-/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Brand, Support, Lifecycle
- Stages: brand trust, incident comms, retention, technical seo


## Why this can grow

A status page only earns trust if customers can still reach it when the product feels shaky. Atlassian recommends using a domain that is separate from the main site because the dedicated page should stay available even when the primary domain or DNS provider is part of the incident. That makes the status route more than a branding choice. It becomes a reliability surface. When the URL is stable, branded, and technically separate, teams have a better chance of getting customers to check the page before they flood support or assume the company has gone dark.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For retention, I would watch the second and third use, not just the first click. A tactic is real when it changes a habit. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where dedicated status domain before first incident can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Brand and Support channel.
3. Use the evidence from support.atlassian.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Statuspage advises teams to configure a custom domain and says it is best practice to use a dedicated domain that is separate from the one hosting the primary site, so visitors can still access status updates during a DNS outage.

## Adjacent tactics in the same lane

- [Atlassian TXT verification before CDN hides status CNAME](/growth-ideas/atlassian-txt-verification-before-cdn-hides-status-cname/) - same source, 1 shared channel, 1 shared stage
- [Scheduled maintenance reminder before the window opens](/growth-ideas/scheduled-maintenance-reminder-before-the-window-opens/) - 3 shared channels, 2 shared stages
- [Component-level status subscriptions before broad blasts](/growth-ideas/component-level-status-subscriptions-before-broad-blasts/) - 2 shared channels, 2 shared stages
- [Customer-facing docs on a brand subdomain](/growth-ideas/customer-facing-docs-on-brand-subdomain/) - 2 shared channels, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The status page should answer before the ticket does](/blog/the-status-page-should-answer-before-the-ticket-does/) - brand trust, incident communication, support deflection

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.