A Substack publication lives on a subdomain such as www: add the domain in Substack first, then point it with the CNAME Substack gives you — target.substack-custom-domains.com on live publications. The root can redirect to it with an A record to 3.231.35.217.
The records to add
| Name | Type | Value |
|---|---|---|
www | CNAME | target.substack-custom-domains.com (the target Substack shows) |
@ | A | 3.231.35.217 — optional: redirects the root to www |
Add the domain in Substack (Settings → Domain) before creating the CNAME. Newsletters still send from @substack.com.
| Cost | A one-time fee |
| Certificate | Up to 36 hours |
Check your domain
Enter your domain: we look up its records and compare them with what Substack expects — the root, www, and any record left over from before.
Step by step
- In Substack, open Settings → Domain and add the domain with its subdomain (www.example.com).
- At your DNS host, add the CNAME Substack shows.
- Optionally, point the root at 3.231.35.217 so it redirects to www, removing other root A records.
- Use “check status” in Substack’s domain settings.
The certificate
Substack sets up the certificate once the CNAME resolves — up to 36 hours. Cloudflare’s proxy must be off.
Common mistakes
- A bare domain without a subdomain — Substack does not support it.
- Creating the CNAME before adding the domain in Substack.
- Cloudflare’s proxy switched on.
Sources
Records checked on 26 September 2026 against these official sources:
- Substack support article 360051222571 — support.substack.com
- Substack support article 360051222691 — support.substack.com