Moving a cPanel site to Cloudflare without breaking mail: a small planning tool

I moved a small cPanel-hosted site’s DNS to Cloudflare and had the agent help me plan it. The risky part isn’t the website, it’s everything else in the zone: mail, webmail, the control panel, DKIM, autodiscover. Cloudflare’s proxy only carries web traffic, so proxying the wrong record quietly breaks mail. We turned the plan into a reusable tool: it reads the zone export, decides record by record what can be proxied (with a reason), writes a Cloudflare-importable zone with an explicit proxied flag on every A, AAAA and CNAME record, a checklist with SPF and MX warnings, and a before/after DNS check. It also writes WAF rule templates where the private header secret stays in an environment variable. Standard-library Python, 54 tests, example data only. It’s public and MIT licensed. #buildinpublic

Repo: GitHub - globe-teck/cpanel-cloudflare-cutover: Plan, export, and verify a cPanel DNS zone cutover to Cloudflare: proxy decisions, SPF/mail checks, import file, before/after diff · GitHub

AI Researcher & Founder at Globe Teck