>And then I realized that I had to hand them over my DNS? Uhh, no. It could have been "set nameserver to ours in your DNS console".

>And also there was the recent SSL spoofing they're doing even with DNS with no hosted websites. And they charge money to send a revocation.

What's your threat model here? That cloudflare will go rogue and... MITM your users? Can't they do that even if they're not in charge of your DNS? Even if you point an A record to them, that's enough to get a certificate via an ACME http-01 challenge[1].

[1] https://letsencrypt.org/docs/challenge-types/#http-01-challe...

You don't have to. In fact there are some TLDs that they don't even support.

You just need to configure the nameservers and that's it. That's how I do it for mine.

> It could have been "set nameserver to ours in your DNS console".

... that's how it works? They give you the nameservers to use, you set your domains up with them.

You can register a domain through them, but don't have to.

In fairness regarding this particular post, the author admits they were probably violating Cloudflare's ToS, and they knew it.

The folks at CF could have been less obtuse in handling the matter. But at the end of the day this is an online casino breaking ToS and they got spanked.