This functionality could also be very useful for academic libraries. Many libraries use a UCC or SAN certificate to secure their proxy server, which authenticates users to allow them to use the library's subscription databases from off campus. The certificate has to include their proxy server's domain (e.g.
library.university.edu) as well as the domains of any databases utilizing a secure connection (e.g.
database1.com.library.university.edu,
database2.com.library.university.edu, etc.) Purchasing a UCC or SAN certificate is quite costly for libraries, so we usually only do it once a year and there is no way to add additional domains the rest of the year. I am just learning about the Let's Encrypt project, but it sounds like this could be a better way for libraries to handle this common situation.
Regards,
Sanjeet Mann
Electronic Resources Librarian
University of Redlands
http://library.redlands.edu