[deanhills]

Well, CloudFlare helps you mask the real IP on which your domain is hosted, of course if you're not using email services on the same domain (MX and TXT records aren't masked). In case you're aware, there are various types of flood attacks, DDoS on a website is just a thing, but attackers can cleverly block you out from logging into your server if they know the IP. 

Being behind CF isn't hiding as such, it's just extra protection. Moreover, if you report a website behind CloudFlare with sufficient proof, they will remove it, exposing the origin IP. 

That being said, I not only use CF for protection, there are other reasons too. For instance as I had highlighted earlier, I use DNSSEC on my project domain, PorkBun as a registrar doesn't support DNSSEC on it's authoritative DNS, hence, you need a provider, CF in my case, free and secure. :-)

Thanks for the feedback @sohamb03. Agreed that Cloudflare has many benefits. Particularly for those looking for DNS. However I was responding to your comment about the combo of a lower level TLD like dot.xyz with Cloudflare being a better option to use than a higher ranking dot.com domain. Cloudflare has many benefits, but if I have to choose between a dot.com Website and a domain like dot.xyz with Cloudflare, then the dot.com Website would be more credible for me. Dot.com is also very cheap relative to the other TLDs.