[Sn1F3rt]

I wouldn't recommend CloudFlare as a choice over .com.  Any reputable company when dealing with traffic would rather be more suspicious of someone who is "hiding" behind CloudFlare and not clearly identifiable, than being out in the open with a reputable .com domain.

Only time when I do have respect for use of CloudFlare services, is when big companies like hostus.us or linkedin use the services to filter out bots.  But if I can't recognize the identity of the Website when CloudFlare is used, I start to doubt the credibility of the Website.

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. :-)