3 ms·
While it seems easy, there are lots of challenges with this where I work. We have 10+ different 'top level' domains (*.example.org), lots of sub-sub domains ex
by joelcollinsdc 12y ago
While it seems easy, there are lots of challenges with this where I work. We have 10+ different 'top level' domains (*.example.org), lots of sub-sub domains example.example.example.org, and route everything through an external CDN. Rough back of the napkin calculations for 100% SSL coverage with our current setup and provider is $10k/month, and that doesn't cover maintenance overhead expenses (my salary) which adds up probably to more than anything we'd pay to a SSL cert provider or CDN provider.
- falcolas 12y agoTen wildcard certificates would run you in the $1-5000 range a year. A few CDN specific certificates another grand or so a year. Maintenance costs shouldn't change, unless you're contract only (and SSL only adds one additional bottleneck per year or two over running the base web servers). I'd be curious to hear how yoru costs would change, as well as where the $10k per month figure comes from. The benefits of encrypting (or at least offering encryption) to your customers would be very fairly significant.
- joelcollinsdc 12y agothe certificates themselves are a small fraction of the cost, our cdn provider's monthly costs for hosting the certificates are the lions share.
- captn3m0 12y agoWon't alternative hostnames field help you out with that?
- joelcollinsdc 12y agoyes 40-50 alternate hostnames can be added per cert. There is significant overhead to managing these and that still means in the most extreme case we could require several SAN certs to get full coverage.
- Dylan16807 12y agoI've never understood why there isn't a true wildcard method that can support naked domains and multiple levels of subdomain.