Skip to main content
Custom domains let you publish a Squasher status page on your own subdomain so customers see your brand, not ours. Instead of sharing a link like app.squasher.ai/status/..., your customers visit status.yourcompany.com and see a fully branded page powered by Squasher. Custom domains are available on Pro and higher plans. Free pages use the managed {your-slug}.status.squasher.ai subdomain.

​
How it works

  1. You register a custom domain in the Squasher dashboard.
  2. Squasher gives you a CNAME record to add in your DNS provider.
  3. Once DNS propagates, Squasher verifies the record and provisions an SSL certificate.
  4. Your status page is live on your domain.
The page is served by Squasher’s managed status-page delivery layer, so it loads quickly and stays available even during incidents affecting your own application.

​
Setup

​
1. Open your status page settings

Navigate to Status Pages in the Squasher dashboard and expand the status page you want to configure.

​
2. Add a custom domain

In the Custom domain section, enter the subdomain you want to use. For example:
Click Add domain.

​
3. Create the DNS record

Squasher will show you the exact CNAME record to add. Go to your DNS provider and create:
Only subdomains are supported (like status.example.com). Root/apex domains (example.com) are not supported.

​
4. Wait for verification

After you add the CNAME, come back to the Squasher dashboard and click Recheck. The status will progress through:
  • Pending DNS — waiting for your CNAME record to propagate
  • Pending SSL — DNS verified, SSL certificate is being issued
  • Active — your custom domain is live
DNS propagation and SSL issuance typically complete within a few minutes.

​
Cloudflare DNS quick setup

If you use Cloudflare for DNS, follow these steps:
  1. Open your Cloudflare dashboard and go to DNS > Records.
  2. Click Add record.
  3. Set the type to CNAME.
  4. Enter the subdomain in the Name field (e.g., status for status.example.com).
  5. Enter edge.status.squasher.ai in the Target field.
  6. Important: Set the proxy status to DNS only (grey cloud). Disable the orange-cloud proxy so Squasher can complete SSL certificate verification.
  7. Click Save.
If you leave the Cloudflare proxy (orange cloud) enabled, SSL verification will fail because Cloudflare intercepts the TLS handshake. You can re-enable the proxy after the status shows Active if you want Cloudflare’s CDN in front.

​
5. Share the URL

Once the status shows Active, your status page is live at https://status.example.com.

​
Managed subdomains

Every status page also gets a free managed subdomain at:
This is available immediately when you create a status page, before any custom DNS setup. You can share the managed subdomain right away and add a custom domain later.

​
What the page includes

Your public status page shows:
  • Overall system status (healthy, degraded, outage, maintenance)
  • Individual component health with linked monitor counts
  • Active incidents with severity and status
  • Recent incident history
  • A “Powered by Squasher” footer
The page theme uses the accent color, headline, and support URL you configure in the status page settings.

​
Frequently asked questions

Not currently. Only subdomains are supported (e.g., status.example.com, health.example.com). Root domains require DNS flattening which adds complexity we plan to support later.
Each status page supports one custom domain. Your plan controls how many status pages you can publish.
Yes. Squasher automatically provisions and renews SSL certificates for your custom domain. No manual certificate management is needed.
Most DNS providers support CNAME records on subdomains. If yours doesn’t, check if they offer CNAME flattening or ALIAS records as alternatives.
Yes. Click Remove next to the hostname in the dashboard. The SSL certificate will be cleaned up automatically.
Yes. The status page is served independently of your application. Even if your servers are down, customers can still check your status page.

​
Agent handoff

Use this prompt for custom-domain setup:
Agents should not invent DNS targets. Use the dashboard, public API, CLI, or MCP Code Mode output for the exact record value.