Connect your domain at Cloudflare
Add the certificate and website records in Cloudflare DNS with the proxy off; Cloudflare flattens the root CNAME for you.
Provider steps checked November 18, 2026. Provider dashboards change; if a button has moved, the official help links at the bottom have the current wording.
You’ll add two or three records in your Cloudflare account: one that proves you own the domain, and the ones that point it at your site. It takes about 10 minutes, it can be undone, and it doesn’t touch your email.
Your Staticbot deployment page shows the exact values to paste, with a copy button next to each, and checks whether Cloudflare is already answering with them. Keep it open next to this guide.
Before you start
- Set Proxy status to “DNS only” (grey cloud) on every record Staticbot gives you. A proxied record answers with Cloudflare’s own addresses instead of the record, so the certificate record can’t be verified.
Open the DNS records at Cloudflare
- Log in to the Cloudflare dashboard and select your domain.
- Go to DNS → Records.
- Click Add record.
Name and Target are Cloudflare’s names for the two boxes you fill in. Type only the part before your domain. Use @ for the domain itself.
Server-rendered app hosted on Cloudflare? Its deployment page lists TXT records and a CNAME on www pointing at apps.staticbot.app instead of the records below. Add them in the same form, with the same Name rule.
Step 1: Add the certificate record
This record lets Amazon issue the HTTPS certificate for your domain. It doesn’t change where your site or email points. Add one record per certificate record shown on the deployment page:
Save, then go back to the deployment page and click Check my records. Staticbot asks Cloudflare’s own servers, so you see the answer within seconds. Once it shows Found, the certificate is usually issued within a few minutes.
Step 2: Point your domain at your site
The deployment page shows these records once the certificate is issued. If your site lives on a subdomain such as app.yourdomain.com, you only add one CNAME for it.
For yourdomain.com (the domain itself):
Cloudflare flattens a CNAME on the root automatically (CNAME flattening), so the bare domain works.
For www.yourdomain.com:
- Prefer not to type records? On the Staticbot deployment page you can connect your Cloudflare account with a scoped API token and Staticbot writes these records into your zone. Optional.
Check it worked
The deployment page checks each record and tells you what it sees: Found, Not found yet, Wrong value, or Domain typed twice (the domain was typed into the Name box). Most records show up within a minute. Your browser may keep showing the old page for a while after that; a private window shows the new one sooner.
Working with an AI agent connected to Staticbot? Ask it whether your DNS records are live; it runs the same check.
Common problems at Cloudflare
- The certificate stays pending although the record exists
- Check the record’s Proxy status. It must be “DNS only” (grey cloud).
Advanced: change nameservers instead
Instead of adding records, you can point the domain’s nameservers at Staticbot. You then add no records at all: the certificate and the site, the domain itself included, are set up automatically.
It’s the right choice when you don’t use the domain for anything else yet: no email on it, no other subdomains. The deployment page recommends it in that case. If the domain has email, Staticbot copies the email records it can see on the domain itself before you switch; records on other names (such as blog.yourdomain.com or email signing keys) have to be re-created, so adding records is usually the safer route there. The deployment page only offers the switch when it’s safe to.
At Cloudflare:
Domains registered at Cloudflare can’t point at another DNS provider. Keep your nameservers and add the records (or connect Cloudflare on the deployment page).
More about what moves and what to check: changing nameservers.
