Skip to main content

D2. Set up Cloudflare

What this page helps you do​

Connect your domain to Cloudflare so you can manage DNS and basic protection in one place.

Why it matters​

Cloudflare is a practical default for many builders because it gives you one place to manage DNS, add HTTPS support, and turn on basic traffic protection.

You should already have​

  • a domain you control
  • access to the place where the domain was bought
  • a destination for the app, such as a hosting provider or server

Skip this page if​

  • your domain is already in Cloudflare and working

Then go to B4. Already have domain or D3. Point your domain to your app.

What to do​

  1. Create a Cloudflare account if you do not have one.
  2. Add your domain to Cloudflare.
  3. Review the imported DNS records carefully.
  4. Update your nameservers at the domain registrar to the Cloudflare values.
  5. Wait for the nameserver change to finish.
  6. Confirm Cloudflare shows the domain as active.

Once Cloudflare is active, you can manage the records that send traffic to your app.

Use Cloudflare as the DNS layer even if the app itself is hosted somewhere else.

For most first launches:

  • keep the setup simple
  • avoid changing many DNS records at once
  • make one change, wait, then confirm it worked

Common mistakes​

  • forgetting to change the nameservers at the registrar
  • deleting imported records too quickly
  • changing records in the old provider after Cloudflare becomes the real DNS source

Next step​

Go to D3. Point your domain to your app.

Advanced notes​

If email already uses the domain, be extra careful with DNS records. Small mistakes can break mail delivery along with the website.