LanguageGB
Security & SSL

Cloudflare-ready guidance

Use Cloudflare carefully for DNS, proxy, SSL, and edge protection.

What this covers

Cloudflare can improve DNS management and security, but incorrect records can break websites, email, SSL, or app routing.

Before you start

Prepare the domain, zone ownership, current DNS records, email records, target service, and rollback expectation.

How to do it

  1. List existing A, CNAME, MX, TXT, and verification records.
  2. Confirm which records are website/app records and which support email.
  3. Preview DNS changes before applying them.
  4. Change one approved record at a time when possible.
  5. Verify website, SSL, and email after any DNS change.

What our team checks

Support reviews zone ownership, allowed records, DNS change preview, rollback plan, and whether a mutation capability is enabled.

Next step

Use the Domains page for read-only DNS visibility or ask support before a production DNS change.

Contact Support