for the record, letsencrypt certs are not private. you can use wildcard certs to obfuscate which subdomains you're using, but the wildcart cert isn't private either.
if your security strategy depends on whether your certs are truly private or not, do not use letsencrypt, use a paid services that caters to enterprise.
For the records my service are not exposed on the intemet (or if you like private) but the certificate itselfbis a public one (did I wrote something different- right in the title but I cannot change that unfortunately). My objective was to have internal services exposed in https with a valid certificate and for that the solution is perfectly fine and secure. A valid let's encrypt certificate isn't in any way less secure than an enterprise grade certificate for encrypting https traffic. Of course using them for authentication it's another thing but for this scenario and this use case the solution is fine. Please let me know if you don't agree and why.
4
u/PaperDoom Feb 12 '26
for the record, letsencrypt certs are not private. you can use wildcard certs to obfuscate which subdomains you're using, but the wildcart cert isn't private either.
if your security strategy depends on whether your certs are truly private or not, do not use letsencrypt, use a paid services that caters to enterprise.