Hello!
This is actually a very common issue when migrating a domain away from Netlify to a new host using Cloudflare. The presence of the Netlify 404 page means your domain’s traffic is still physically reaching Netlify’s servers, even though the domain was removed from your account.
Here are the specific steps to resolve this, starting with the most likely culprit:
**1. Check Cloudflare for Leftover Netlify Records**
When you changed your nameservers, Cloudflare automatically imported your old DNS records.
* Log in to your Cloudflare dashboard and go to **DNS > Records**.
* Look at your A and CNAME records for the root domain and www.
* If they are still pointing to [yoursitename].netlify.app or Netlify IP addresses (like 104.x.x.x or 75.x.x.x), you need to delete them and replace them with the IP address or alias provided by your **new** hosting provider.
**2. The “Cloudflare for SaaS” Zone Overlap (Hidden Issue)**
If your DNS records in Cloudflare are 100% correct, you are likely stuck in a routing loop. Netlify uses Cloudflare Enterprise under the hood. Sometimes, Netlify’s custom hostname routing overrides your personal Cloudflare account.
* **The Fix:** If this is happening, you cannot fix it yourself. You will need to wait for a Netlify Support staff member to reply to this thread and manually *“purge the domain marsburgadvisory.com from their Cloudflare for SaaS configuration”*.
**3. Purge the Cloudflare Cache**
Cloudflare might have cached the Netlify 404 page while you were making changes.
* In Cloudflare, go to **Caching > Configuration** and click the **Purge Everything** button.
**4. Clear Your Local Cache**
To make sure you aren’t seeing a locally saved version of the site, try opening marsburgadvisory.com in an Incognito/Private window, or test it on your phone using cellular data (with Wi-Fi turned off).
Double-check Step 1 first, and if your DNS records are definitely pointing to your new host, leave a comment here asking Netlify Support to check for the SaaS routing overlap.
Hope this helps!