Custom domain

Serve your support form on your own hostname, with SSL provisioned automatically.

A custom domain lets customers visit your support form at a URL you own — for example, support.acme.com — instead of only the default your-slug.support-page.dev address. Once your DNS record verifies, SupportPage automatically issues and manages an SSL certificate for your domain — there's no certificate to generate, upload, or renew yourself.

Open Support page → Settings → Custom domain in the dashboard.

Why use a custom domain

  • Brand trust — the URL matches your product
  • Consistent cookies and SSO context — when embedded or linked from your app subdomain
  • Email alignment — easier to explain in docs ("visit support.acme.com")

Custom domains are typically available on paid plans. Confirm eligibility in Invoices and subscription.

Setup overview

Rendering Chart
  1. Enter your desired hostname (subdomain recommended — support.example.com, not always apex example.com).
  2. SupportPage shows a single CNAME record to create, pointing your hostname at your SupportPage subdomain. No other records are required to set up.
  3. Add that record at your DNS provider (Cloudflare, Route 53, etc.).
  4. SupportPage checks DNS automatically — there's no manual "Verify" click required. It's checked on a background schedule and, while setup is in progress, the dashboard also refreshes the status for you every 30 seconds.
  5. Once the record resolves correctly, SupportPage requests an SSL certificate for your domain. This usually finishes in well under a minute.
  6. When the certificate is active, your hostname starts serving the support form over HTTPS, and you'll get an email confirming it's live.

Domain status

The custom domain settings page shows one of these statuses while your domain is set up:

StatusMeaning
PendingYour CNAME record doesn't resolve to the expected target yet. Checked automatically every 30 seconds.
ProvisioningDNS looks correct — SupportPage is issuing an SSL certificate for your domain. Usually under a minute.
VerifiedDNS and SSL are both good. Your support form is live on the custom domain, and SupportPage continues monitoring the record.
DisconnectedA previously verified domain's CNAME stopped resolving correctly (for example, the record was edited or removed). Restore the record and it will automatically re-verify — no need to re-enter the domain.

DNS record type

Exact values are shown in the dashboard at setup time.

RecordPurpose
CNAMEPoints your subdomain at SupportPage's hosting endpoint. This is the only record needed — no TXT or other verification record is required.

Apex vs subdomain

ChoiceRecommendation
Subdomain (support.example.com)Preferred — simple CNAME
Apex (example.com)Often requires ALIAS/ANAME or flattening; not always supported

Use a dedicated subdomain for support intake when possible.

Default URL after custom domain

The original slug.support-page.dev URL keeps working alongside your custom domain — it's the underlying address your CNAME points at, so it's never disabled. Prefer linking the custom domain in customer-facing materials once it's verified.

Troubleshooting

IssueWhat to check
Stuck on PendingDNS TTL; typos in hostname; proxy-only mode on Cloudflare (switch the record to DNS-only / grey cloud — a proxied record breaks certificate issuance)
Stuck on ProvisioningUsually resolves within a minute on its own; if it doesn't, double-check the CNAME target still matches exactly what SupportPage shows
Shows DisconnectedSomething changed or removed the CNAME record at your provider — restore it and SupportPage will re-verify automatically, no re-entry needed
Wrong page shownHostname attached to a different support page in your account
Works locally, fails for othersIncomplete propagation — use dig or online DNS checkers

See also FAQ — custom domain.

Removing a custom domain

  1. Update links in your app and docs to another URL first.
  2. Remove the domain in SupportPage settings — this also deprovisions the SSL certificate for that hostname.
  3. Delete DNS records at your provider when no longer needed.

Customers with bookmarked URLs will hit DNS or certificate errors after removal.