User blog comment:DaNASCAT/FANDOM Increasing HTTPS Support To Improve Security/@comment-5973717-20171027161726/@comment--20171027184239

Kocka's explanation is correct as to why this approach will not work for our needs. There are a number of practical issues to consider too - we want to be able to ensure that whatever certificates we procure now apply to all future URLs - we don't want to get into a situation where we get certificates based on the URLs of wikis we currently have and then let someone create new wiki the next day with a URL that does not fit under this pattern. Additionally, different languages on the same topic may not necessarily use the same domain in their URL. Marvel is a great example of that. The main EN URL is "marvel", while many of the other affiliates use "marveldatabase". Some wikis about the same topic may use differently translated phrases as well. That's a lot of manual oversight in a process that is already going to be difficult. We'd rather focus on a cleaner solution - one simple URL change that will solve all the current URLs and handle future URLs.