Connect a Cloudflare domain

Have your DNS and proxy instructions ready

Read our before-you-start checklist and guide to keeping your email. Your Website People will provide the exact record types, names, values, and proxy setting for your website. If the proxy setting is missing, ask us for it before saving. Each website has its own connection instructions.

Confirm Cloudflare currently manages your DNS, even if you purchased the domain elsewhere. Keep your existing nameservers and email service, and save a screenshot of the current records. If a hosting partner manages your Cloudflare setup, the DNS controls may be in that partner’s account instead.

Edit the requested website records

1. Sign in to Cloudflare, select your domain, and open DNS → Records.

2. Find the website record identified in your launch instructions and select Edit. If the record is missing, select Add record.

3. Select the supplied record Type and enter its name and destination exactly as instructed. An A record uses an IPv4 address; a CNAME uses a destination hostname.

4. Set Proxy status to the value we supplied. Leave TTL at the supplied or default setting, then select Save.

5. Repeat for the other website records in your instructions. Tell us about any conflicting existing destinations before removing records.

Take care with the cloud setting

Proxied sends website traffic through Cloudflare. DNS only sends visitors directly to the destination. This choice can affect verification and how your site connects. Cloudflare recommends DNS only for a hosted platform that does not explicitly support its proxy; follow the setting we confirm for your website.

Replace only the conflicting website records we identify for the same hostname. Keep unrelated records and existing email services active. Check with us before canceling old hosting if it also provides email.

Confirm the connection before wrapping up

Notify Your Website People when the changes are saved so we can verify your site. DNS refresh timing depends on the records’ TTL and cached previous answers. A saved change can take time to appear on every network; there is no single instant switch for all visitors.

Visit your domain with and without www, using HTTPS. Confirm the correct site loads without a certificate warning, then send and receive a test email.

If the old site still appears, try another network. A private browser window can help with browser state but does not clear external DNS caches. Share any error or unexpected result with us. We will help confirm the launch before you retire the old website.