Getting started with status pages

Status pages are available on all plans, including the 30-day free trial.

1. Create the page

Go to Settings → Status pages → New status page. Pick:

• Title — what visitors see at the top of the page.
• Slug — three to thirty-two lowercase letters, digits, or hyphens. No leading or trailing hyphen. The slug becomes the public URL: domaincare.io/status/<slug>.

The page returns 404 to public visitors until you publish.

2. Add domains

Select one or more domains from your org. Each domain you check expands to show its own set of checks — pick which ones visitors see for that domain. Defaults: Uptime, SSL, DNS.

• Up to 20 domains per status page.
• Drag the handle on each domain card to reorder them.
• The layout picker lets you choose Grouped by domain (sections) or Flat list (all checks in one column, labeled by domain).

3. Preview and publish

Click Publish to make the page live. When publishing a page with multiple domains, a confirmation shows which domain names will be publicly visible — review before confirming.

The public page is live at domaincare.io/status/<your-slug>.

4. Edit after publishing

Changing domains, checks, layout, or title takes effect on the next page revalidation (up to 60 seconds). Unpublish at any time to return the page to draft.

Limits

• 20 domains per page.
• At least one check per domain.
• Slugs follow ^[a-z0-9](?:[a-z0-9-]{1,30}[a-z0-9])?$. Reserved slugs are rejected — see slug rules.

API and MCP

Status pages can also be managed via the REST API (/api/v1/status-pages) and the domaincare-mcp package (v2.0.0+). Both accept a domains array with per-domain check selection. See the API docs for request/response examples.

Why no subscribers or custom domains?

We deliberately did not ship email / RSS / webhook subscribers or custom hostnames. Most teams told us they're already broadcasting to their own customer channels (Slack, X, in-app banners), and a single canonical URL keeps the surface simple. We'll revisit once traffic shows demand.