If your services are private they should be behind access authorization or completely private access. Scanning should be a non-issue.
You can further mitigate scanning by getting wildcard certs, putting A/AAAA records on an obfuscated sub-domain rather than the base domain, and not using wildcard CNAME’s.
If they services are public you should be using a CDN anyway. If you don’t like the way Cloudflare does things they’re not the only CDN around, but some of the privacy issue is moot when running a public service.
I wouldn’t say the privacy issues are moot when running public services, as metadata is quite valuable. Cloudflare will get a lot of information like who your visitors are, how often they visit, how long are they staying on a page yada yada
If your services are private they should be behind access authorization or completely private access. Scanning should be a non-issue.
You can further mitigate scanning by getting wildcard certs, putting A/AAAA records on an obfuscated sub-domain rather than the base domain, and not using wildcard CNAME’s.
If they services are public you should be using a CDN anyway. If you don’t like the way Cloudflare does things they’re not the only CDN around, but some of the privacy issue is moot when running a public service.
I wouldn’t say the privacy issues are moot when running public services, as metadata is quite valuable. Cloudflare will get a lot of information like who your visitors are, how often they visit, how long are they staying on a page yada yada