Greetings,
Thank you for asking.
Two possible scenarious:
- Using Cloudflare for your domain name through SiteGround as a SaaS integrator → any change you need and want to make, you do it through SG interface and contact them for any issue
- Using Cloudflare for your domain name individually using your own Cloudflare account and your set of Cloudflare nameservers at your domain registrar and pointing DNS records to the SiteGround hosting. Therefore, you create your own Cloudflare account and individually and manually add your domain name to your Cloudflare account and change domain nameservers to point to Cloudflare nameservers at your domain registrar.
If you would like to use the 2) option, but currently using 1) as far as I understand, then:
- remove your domain name from your CF account
- disable Cloudflare at SG interface
- contact SiteGround to unhook the domain and remove any existing CNAME setup / SaaS connection and to disable DNSSEC (if it was enabled?) and remove any existing DS records (if they were added)
- create your own Cloudflare account
- wait for 24 hours
- add your domain name to your CF account
- change domain nameservers at your domain registrar to the provided pair from Overview tab at CF dashboard
- wait for 24 hours
- double-check your DNS records at CF dashboard for your domain name
It knows to be an issue when we use some hosting providers which enable SaaS for our domain name/website.
Kindly, ask them to re-check this and remove/delete if so.
I’d suggest you to follow the instructions from the article below as they are related to any SaaS integrator:
If they resolve this and after 24 hours you still see this notice in your Cloudflare dashboard for your CF account, you might need to remove the domain name from your CF account and re-add it again (and then change the domain nameservers at your domain registrar).