I'm working with the registry for .wiki, a new generic top level domain set for public availability in June 2014. We're going to be giving away hosted wikis to registrants of .wiki domains and I'd like to use only https across the board on these wikis.

Purchasing an ssl cert for each second level domain is cost prohibitive and I see from Can a wildcard SSL certificate be issued for a second level domain? that web browsers reject *.tld certs.

We control the nameservers and webservers for all the .wikis we host and prepared for legwork if need be (e.g., convincing browser manufacturers to support a *.wiki cert).

What mechanisms can you think of that would allow us to inexpensively offer https across a wide swath of the *.wiki space?

2 Answers 2


Your best bet is to approach a certificate authority to get a signing certificate with authority for that TLD. They should be able to issue you an intermediate certificate, but you will need to be ready to take on CA level security to do it. You could also try to get established as your own CA, but that would probably be more costly.

  • This is a good idea, thanks. I'm also considering the various reseller programs ... that at least would get the cost of the certs down as far as possible. Still too expensive for the free wikis though. Feb 21, 2014 at 4:53

I don't think this is going to work. Some of the hostnames under .wiki will be under your control. But a wildcard cert for the TLD would allow you to masquerade as the authoritative server for any .wiki hostname, even ones that you don't provide hosting for.

  • So a single *.wiki cert isn't a workable solution. Feb 21, 2014 at 4:26
  • Not unless you're planning to host every single domain under the .wiki TLD. Feb 21, 2014 at 18:16
  • Nope, just a subset of .wiki. Thanks for the unambiguous squash of this approach ... also very helpful. Feb 21, 2014 at 20:23

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .