Domain and DNS
Every site is reachable at {slug}.spacesite.dev as soon as you publish. To serve it on your own domain — for example docs.example.com — you add one DNS record that points the name at SpaceSite. SpaceSite uses Cloudflare for SaaS, so the certificate is issued and renewed for you; there is nothing to install on your side.
1. Add the domain in the panel
In Space settings → SpaceSite, open Domain and enter the hostname you want to use (a subdomain such as docs.example.com or help.example.com). The panel then shows the exact CNAME target to create and tracks the status until the domain is active.
2. Create the CNAME record
At your DNS provider, create a CNAME record for the hostname, pointing at the Cloudflare for SaaS target shown in the panel:
| Type | Name (host) | Value (target) |
|---|---|---|
CNAME |
docs (i.e. docs.example.com) |
the target shown in the panel (e.g. cname.spacesite.dev) |
Use the exact target from the panel. Set TTL to Auto or a low value (300 seconds) so changes take effect quickly. SpaceSite validates ownership and issues the TLS certificate automatically once the record resolves.
3. Wait for propagation
DNS changes and certificate issuance usually complete within a few minutes, but can take up to 24 hours depending on your provider and the previous TTL. The panel moves the domain through Pending → Verifying → Active; when it is Active, the site serves on your domain over HTTPS. You can check propagation yourself:
dig docs.example.com CNAME +shortshould return the SpaceSite target.- Until the certificate is issued, the browser may warn about the connection — this clears on its own once the domain is Active.
The {slug}.spacesite.dev address keeps working after you add a custom domain, so you never lose access while DNS propagates.
Common errors
| Symptom | Cause and fix |
|---|---|
| Domain stuck on Pending | The CNAME is missing or points elsewhere. Re-check the record name and target against the panel. |
CNAME cannot coexist / record rejected |
A CNAME cannot sit next to other records on the same name. Use a subdomain (docs), not the bare root example.com. |
| Points at the wrong place | An old A/AAAA or a different CNAME is still present. Remove the conflicting record, keep only the SpaceSite CNAME. |
| Proxied / orange-cloud at an existing Cloudflare zone | If the hostname is already in your own Cloudflare account, set the record to DNS only (grey cloud) so SpaceSite can complete verification. |
| Certificate warning after going Active | Usually a cached old certificate. Hard-refresh, or wait for the panel to confirm Active. |
Still stuck? Email info@spacesite.dev with your hostname and we will check the record. Next: Privacy, security and support, or back to Publishing and sync.