Hostinger do that – they use silly tricks like having a blank user agent, use go-http, or test from random high risk countries when testing sites so get blocked by WAF rules
All of my Hostinger sites regularly show as disconnected but still work happily - just ignore the message
If you were cynical, which I am, you might see it as a deliberate attempt to try to prevent you using Cloudflare
You could check in your security, analytics or events to see why they are blocked
Note that apparently you can have DNS (NS) at Cloudflare, but your server (A) at Hostinger. But in your case the A record seems to point to a Google IP address, so I have no clue which role Hostinger might have here. Do you use them at all?
Name Server: ALGIN.NS.CLOUDFLARE.COM
Name Server: MAY.NS.CLOUDFLARE.COM
Name Server: NS1.DNS-PARKING.COM
Name Server: NS2.DNS-PARKING.COM
DNSSEC: signedDelegation
In order to activate your domain in a full setup on Cloudflare, you must have your Cloudflare nameservers, and only your Cloudflare nameservers, assigned at your registrar. You also have DNSSEC enabled, which is fine as long as it is using the values provided in your Cloudflare dashboard.
i have removed the hostinger nameserver , deleted dnssec , and changed proxied dns to dns only , and waited for 60 hour but i am ot able to search my website becase of it and hostinger forcing me to use their nameserver otherwise my domain gonna expire becase of inactivness
The hostinger message of “disconnected” can be ignored - all our hostinger sites show as “disconnected” as we use Cloudflare as registrar and nameservers for them, with hostinger just as the hosting and they all work happily
The hostinger checking system just gives that “error” message when you dont use their nameservers - despite the fact that they give good clear instructions on setting sites up with Cloudflare
The hostname photoedito.com points to an IP address not managed by Cloudflare. That IP address doesn’t appear to have a valid SSL certificate for your domain, If that is the correct IP address you’d need to work with your hosting provider to determine why the website doesn’t load correctly.
www.photoedito.com points to:
www.photoedito.com. 300 IN CNAME connect.hostinger.com.
connect.hostinger.com. 3600 IN A 34.120.137.41
Why that doesn’t display a valid SSL certificate is also a question for the hosting provider. Confirm with them that both entries point to the appropriate location in DNS and they can troubleshoot why there isn’t a valid SSL / provide steps to resolve that.