How to Add a Domain in Cloudflare Easily 2026

Logging into Cloudflare drops you on Account home, a dashboard that's useful if you manage more than one property: a Domains card listing each site with its recent traffic, a Workers and Pages card for any deployed projects, Zero Trust security shortcuts, and an Audit logs feed of recent account activity. A Next steps panel nudges you toward things like enabling single sign-on or inviting teammates. Worth a glance, but not required before adding a new domain.

From Domains in the left sidebar, starting the onboarding flow opens a screen titled "Connect your domain" with the subhead "Make your site faster, more secure, and more reliable." It's a single required field, Domain name, with a placeholder like example.com, plus a Continue button and a collapsed link reading "Configure DNS records import and AI crawler preferences" for anyone who wants to adjust the defaults before proceeding.

Typing a domain name and expanding that preferences link reveals two decisions Cloudflare wants up front. The first, "How should DNS records be imported?", defaults to "Import DNS records automatically" (marked Recommended), which scans the domain's current records so mail and hosting entries carry over without re-entering them by hand.

The second, "Control how AI crawlers scrape content for training", defaults to "Block AI crawlers on all pages", with a toggle for "Instruct AI bot traffic with robots.txt" underneath. That second control is a recent addition to onboarding, reflecting how much AI training crawler traffic has grown, and it lets you block that traffic site-wide from the moment the domain connects.

Clicking Continue moves you into plan selection, where the Free tier sits alongside paid options. For a typical small site, Free is enough to get started: it includes DNS management, proxying, and Cloudflare's baseline security features, with paid tiers adding things like advanced page rules, image optimization, and more granular analytics. Nothing about the DNS import or AI crawler choices from the previous screen changes based on which plan you pick here.

After the scan finishes, Cloudflare shows the records it found. Read this screen instead of clicking past it: check specifically that MX records for email are present and that the A or CNAME rows pointing at your hosting are correct.

Cloudflare's own documentation is explicit that the automated scan isn't guaranteed to catch every existing record, so a subdomain or an unusual entry a previous host set up by hand can occasionally be missed. It's easier to add that manually now than to chase down a broken inbox after nameservers have already switched.

If the domain has DNSSEC enabled at its current registrar, turn it off there before doing anything else in this step. Cloudflare's documentation warns plainly that changing nameservers while DNSSEC is still active can make the domain unreachable. You can re-enable DNSSEC through Cloudflare once the domain shows as active.

The last step happens outside Cloudflare: it assigns the domain a unique pair of Cloudflare nameservers, and you need to log into the registrar and replace the existing nameservers with those two values. Cloudflare's own guidance is to allow up to 24 hours for the registrar to process the change, though it's often much faster. The dashboard shows the domain as active once it detects the new nameservers are live, and it rechecks periodically during that window.