TL;DR: This will happen as a result of mostly unrelated cleanup efforts.
To clarify our position here: there were no plans to make the redirect-only domains available over
https://. They were never at any point in time supported, nor do we generate links to them - so all links in existence should be
Even if they were
https://, they wouldn't get the benefits of
https:// anyway, since they're just 301s to the site's real domain). There's really very little reason to take on the certificate complexity and cost to add these additional domains.
Not that being said, this will eventually happen anyway for other reasons. As simply as a side-effect of us shuffling redirects between name.com servers and Cloudflare for redirects. We did this for miyodeya.com for the purposes of existing SE 1.0 links - since they ever existed, not supporting this on name.com's redirect service was causing (effectively) 404s to actual content.
We moved them to our miscellaneous Cloudflare account for the purposes of redirects, supporting
https:// is only a side-effect. But, maintaining 2 ways of doing something when 1 is saner/easier (we're almost done automating this) is just silly. So the plan is to move all these domains to Cloudflare. Here's the list:
I don't have an exact timeline as the main dev on the sync bits for Cloudflare/page rules is currently moving and out for a little while. Roughly, I'd say in the next month or two.