Skip to main content
SiteShi p

How-to guides

Connect a custom domain

What you'll get

Your SiteShip site served at a domain you own (e.g. dailybrew.com) instead of your-slug.siteship.dev. SSL is automatic. The default URL keeps working too — both resolve to the same site.

In the hosted builder

  1. Settings → Domain → Connect domain.
  2. Enter your domain and click Add.
  3. We show you two DNS records to add at your registrar (typically a CNAME or A/AAAA pair).
  4. Wait for verification — usually a few minutes. The dashboard polls automatically; the indicator turns green when DNS resolves.
  5. SSL provisions in the background (Let's Encrypt). Your site is live at the new domain.

If your registrar's DNS is slow to propagate, walk away — it'll be ready when you come back.

Result

  • Your site live at yourdomain.com (and www.yourdomain.com if you set up the second record).
  • HTTPS automatic; HTTP redirects to HTTPS.
  • The original *.siteship.dev URL keeps working — useful for testing and as a fallback.

Common gotchas

  • Apex (root) domains need an A or AAAA record. Subdomains (like www) can use CNAME. We tell you which to use when you add the domain.
  • Existing CNAME conflict. If your apex domain already has any other DNS records pointing somewhere else (Google Workspace MX, an old hosting setup), keep those — only modify the records we tell you to.
  • Slow propagation. DNS can take up to 48 hours globally, but most registrars resolve in minutes. If verification is stuck after an hour, double-check the record values match exactly what the dashboard shows.

Under the hood

Architecture reference → Routing covers how requests resolve to your site. SSL and edge caching are handled by Cloudflare; you don't need to configure either.

Found something out of date? Open an issue. ← All docs