Crypt-LE VS mod_md

Normally you can use the same .csr forever if the domain is the same - I normally use LE64 to generate let's encrypt certificates (which can do wildcards also), but if you're purchasing a certificate rather than generating a free one, and you want to generate it right in IIS, you can follow a guide like this. If you generate a wildcard cert like *.domain.com, you can use it for all your subdomains but NOT generally for domain.com itself (depending on your application). You can use the same certificate for all applications provided they support whatever format the certificate is in; mostly these will be in PEM-style anymore so you have the whole cert chain in one file.

There's already other CAs that (optionally) use ACME to issue. As I understand it from the mod_md readme [1], Buypass basically works (without must staple), Sectigo and ZeroSSL work too, but require an account to be setup.

Are these true alternatives? If not, why not? I don't know where these companies reside.

[1] https://github.com/icing/mod_md?tab=readme-ov-file#known-iss...

Apache mod_md has fallback too, https://github.com/icing/mod_md#acme-failover I'm just a user, not the author, and I didn't try the fallback. I'm more worried about stuff breaking if I switch issuers than certs expiring without me noticing. I've got some embedded junk that hits my website and has weak cert validation, so better to stick with something that works.

Add mod_md to your apache configuration