Fix the SSL certificate, and the redirect follows
Before a browser follows a redirect over HTTPS, it checks a certificate. It connects to the old hostname, checks the certificate there, and only then receives the response that sends it on. If that certificate is missing or expired, the visitor gets a warning instead of the new address.
So the domain you redirect from needs a valid certificate of its own, even if it never serves a page. The articles in this category cover that certificate and everything that depends on it.

Certificates, HSTS and security headers
- How to redirect with HTTPS
- Redirecting a Domain That Used HSTS
- Security Headers on a Redirect: Two Matter, Four Don't
- Shorter SSL Lifetimes: Why Redirects Break First
Why a redirect needs its own certificate
HTTPS is set up before any HTTP response is sent, and a redirect is an HTTP response. A certificate for the destination doesn't help, because the browser hasn't reached it yet. The certificate has to cover the exact hostname the visitor opened, so www and the bare domain both need to be covered. How to redirect with HTTPS covers the setup, and why HTTPS redirects break explains the failures you'll see most. For the order of events, step by step, read how URL redirects work.
Registrars that offer domain forwarding don't all handle HTTPS the same way. Before you rely on one, open the old address over HTTPS and see what happens. The support pages for GoDaddy and Namecheap show how to set up forwarding with HTTPS through redirect.pizza.

What keeps HTTPS on a redirect working
Certificates expire, and their maximum lifetime keeps getting shorter, so renewals come around more often. With automatic renewal, a redirect doesn't notice. Shorter SSL lifetimes: why redirects break first explains why a missed manual renewal tends to show up on a redirect before anywhere else.
HSTS adds a rule of its own. Once a browser has seen an HSTS header from a domain, it sends every request there over HTTPS. Until the policy expires, visitors can no longer click past a certificate error. A domain that once sent HSTS therefore needs valid HTTPS for as long as that policy can live in browsers. That's the point of HSTS, not a flaw in it, and redirecting a domain that used HSTS shows how to handle it.
Of the six security headers that scanners check, only two do anything on a redirect response: Strict-Transport-Security and Referrer-Policy. Security headers on a redirect explains why the other four don't apply.
With automatic HTTPS, redirect.pizza issues a certificate for every domain you add and renews it before it expires, on every plan.