Cloudflare can sit in front of your site for CDN and protection. You must choose who hosts DNS.
Pattern A — Cloudflare proxies; 4GH still hosts the site (common)
- Add the site in Cloudflare.
- At your registrar, set Cloudflare’s nameservers (not
ns1.4goodhosting.com). - In Cloudflare DNS, create A/AAAA (and CNAME) records pointing to your 4GoodHosting server IP from the welcome email or cPanel.
- Orange-cloud the web records; keep mail-related records (MX, SPF, DKIM, DMARC) correct — often grey-cloud for some host records.
- SSL mode: start with Full (strict) once AutoSSL or an origin cert is valid on the server.
AutoSSL note: When Cloudflare owns DNS, cPanel AutoSSL may need a DNS challenge or a Cloudflare DNS API token. If HTTPS fails to issue, open a ticket.
Pattern B — Stay on 4GH nameservers
Use ns1–ns4.4goodhosting.com and skip Cloudflare, or use Cloudflare only as a registrar with DNS still pointed at us (less common).
Email warning
Wrong Cloudflare proxy on mail hostnames breaks email. Keep MX on our mail hostnames from cPanel, and repair SPF/DKIM via Email Deliverability after DNS changes (#2850).