When Stack Exchange transitioned to HTTPS,
meta.*.stackexchange.com subdomains were changed to
meta.* subdomains now redirect to the new
Trying to visit them over HTTPS causes a certificate error.
The justification for the change was given in an answer to that post:
The old Meta URLs will never support HTTPS. The whole point of changing the path to
*.meta.stackexchange.comwas because wildcards cannot use
meta.*.stackexchange.comand we couldn't apply a single certificate to all of the Meta domains. We are not interested in maintaining a bunch of certificates for all the domains just to support an outdated URL scheme that was replaced for the very reason we couldn't support it.
However, since then, Stack Exchange has switched to using Let's Encrypt to manage their certificates. Unlike traditional CAs, using Let's Encrypt makes it very simple for SE to manage their
It seems unlikely that it would be hard for Stack Exchange to use Let's Encrypt to obtain certificates for all of their
*.meta subdomains, since Let's Encrypt (exclusively) allows certificates to be acquired in an entirely automated process, significantly streamlining the certificate creation process.
Adding TLS to these old URI would improve security and eliminate potential TLS errors encountered by users.
Note that I'm not asking for the actual URIs for per-site metas to be changed: I only want TLS to be added to the redirecting domains.