Buttondown Custom Domain Not Verifying
Quick answer
A custom domain stays unverified when DNS records are missing, mistyped, proxied (Cloudflare orange cloud) or clash (NS and CNAME on one name). Match the records in Settings exactly, set Cloudflare to DNS only, then wait.
Most likely fix: Use separate subdomains for hosting and sending
How to fix it
Try these in order — the most common fix is first.
1. Use separate subdomains for hosting and sending
- Use newsletter.example.com for hosting (CNAME) and mail.example.com for sending (NS)
- Never put a CNAME and NS on the same name
Did this fix it?2. Cloudflare users
- Set Proxy status to DNS only (grey cloud) for Buttondown records
- For a root domain using CNAME flattening, add the challenge record Settings shows when required
Did this fix it?3. Re-check the records
- Compare each record with Settings character by character
- Check them with a DNS lookup tool
- Allow time for propagation; Buttondown rechecks hourly
Did this fix it?4. Contact support
- If records are correct and it stays unverified, email support with the domain name
- Buttondown also exposes verification status on its API for debugging
Did this fix it?
Symptoms
Settings shows the domain or records as unverified or pending; archives or sending still use buttondown.com.
Why it happens
- NS and CNAME records on the same hostname
- Cloudflare proxy (orange cloud) enabled on Buttondown records
- Root domain with CNAME flattening needing an extra challenge record
- Records copied with the domain appended twice
- DNS not yet propagated
This guide also covers
- buttondown custom domain not working
- buttondown dns verification
- buttondown cloudflare
Still not working?
If Buttondown keeps failing, you're not alone. See every Buttondown problem users report or the alternatives people switch to.
Done fighting Buttondown? Our small team builds your own Buttondown alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to us