Almost all the Universities using InCommon for ECC certs are scrambling with IT Staff working round the clock to replace their ECC certs chained to the emSign ECC Root CA - G3 before Chrome distrusts the root on October 27.
I think the biggest bottleneck now for them in switching to Lets Encrypt certs is rate limits. Especially the 50 certs per domain slows down the issuance to multiple weeks instead of days.
I am asking, is it possible for Let's Encrypt to increase the rate limits for .edu domains to support a lot of these Universities which are non profit institutions. Obviously this would only be possible if there is a resource availability to do this? But how different would this be like in the past when Let's Encrypt reissued millions of certs due to a bug.
Get a *.domain.edu wildcard. Deploy it everywhere. You are now on let's encrypt. There's nothing wrong with wildcards, and shorter-lived keys make them safer. Data to back that up:
Over the next few weeks, change over what you feel is important to named certs, staying within the rate limits.
I think a big lesson everyone should learn from this is to not bind yourself to any one CA. Things can happen, and getting new certificates shouldn't be a Herculean effort. Have a few providers, and a plan to switch quickly. If you have a centralized deployment system, this can be a very fast change. We war-gamed switching 100 certs from LE to Google and we had it fully deployed in about 10 minutes with CertKit.
Adding to the wildcard suggestion: it works best as a phased plan, not a single big cutover. First inventory every hostname and group them by registered domain, since the 50-certs-per-week limit is per registered domain. Put a wildcard on each busy domain first so public-facing services are covered, then migrate the rest in batches and stagger their renewal dates so they don't all land in the same week again. A wildcard only covers one DNS level, so check for deeper subdomains that will still need their own names. If a domain genuinely can't wait, use Let's Encrypt's rate-limit adjustment request process and include your domain, expected volume, and timeline — and test the whole automation against the staging environment first, so a misconfiguration doesn't burn production rate-limit budget. Having a second CA ready as a fallback is also worth it when a browser distrust deadline is driving the schedule. — Sarah
Consider Google Trust Services, where there is no "50 certs per week per registered domain" limit. If you fully exploited the rate limits, you could issue ~2400 certificates per day, even for a single registered domain (e.g. example.edu).