Get a valid certificate on every domain you redirect
A redirect starts with a request to the old domain. Over HTTPS, the browser checks that domain's certificate before it ever sees the redirect. No valid certificate, and the visitor gets a warning instead of your site. That's why HTTPS redirects break.
It applies to every domain that only exists to redirect: the old domain after a rebrand, typo and defensive domains, campaign domains, retired product names. People reach them over HTTPS through bookmarks and old links, and browsers that hold an HSTS policy for the domain won't try anything else.

Why the certificate matters before the redirect
Since Chrome 68 in July 2018, Chrome marks every HTTP page as "Not secure." Over HTTPS, a missing or expired certificate stops the visitor at an error page, before the redirect runs. Google has also used HTTPS as a ranking signal since 2014.

Renewing certificates by hand across dozens of redirect-only domains is easy to get wrong. One renewal slips, and an old domain that still gets traffic starts throwing errors.

How redirect.pizza handles HTTPS
- A certificate for every source hostname, issued automatically once the DNS points at redirect.pizza, on every plan. More on automatic HTTPS.
- Short renewal cycles. Certificates come from Let's Encrypt and are valid for 45 days, renewed well before they expire. If Let's Encrypt is unavailable, redirect.pizza falls back to ZeroSSL, with 90-day certificates. See SSL profiles.
- Short-lived certificates, valid for 160 hours, if your security policy asks for them. From Pro (Prosciutto e Funghi).
- Current TLS versions, with an A+ rating at Qualys SSL Labs on every plan, including Free (Margherita).
- Wildcard certificates from Pro, issued through a DNS challenge. A certificate for *.example.com covers every subdomain one level deep, such as shop.example.com, but not example.com itself or a.shop.example.com. See wildcard subdomains.
HSTS on the redirect
With HSTS enabled, redirect.pizza sends a Strict-Transport-Security header with a max-age of one year by default. It first upgrades http:// requests to https:// on the same hostname, and only then redirects. That way the policy is set on the old domain before the visitor moves on.
Enable it with care. Browsers remember HSTS for the full max-age, so only turn it on for domains that will keep serving HTTPS. If an old domain already used HSTS, browsers that still hold its policy only reach it over HTTPS, so its redirect has to keep a valid certificate for that reason alone. Here's what that means for a redirect.
Of the six security headers people usually check, only HSTS and Referrer-Policy do any work on a redirect. Why the other four don't is explained here.
What you need to set up
- DNS pointing at redirect.pizza. Detecting the change can take up to 24 hours, although most changes are picked up within an hour. The certificate is issued once it's verified.
- CAA records that allow the issuers. If the domain has CAA records, they must allow Let's Encrypt and Sectigo. Without CAA records, there's nothing to change.
That's it. No certificates to buy, upload or renew.
The HTTPS redirect for your own site
redirect.pizza handles HTTPS for hostnames that point at it. The HTTP to HTTPS redirect for your live site's own hostname belongs in your web server, CMS or CDN. Here's how to redirect with HTTPS on your own setup.
Frequently Asked Questions
A DNS record that says which certificate authorities may issue certificates for a domain. If a domain you redirect has CAA records, they have to allow Let's Encrypt and Sectigo, or redirect.pizza can't get a certificate for it. A domain without CAA records needs no change.
The browser stops at a certificate warning, such as Chrome's "Your connection is not private" page, before the redirect can run. If the domain uses HSTS, the browser doesn't even offer a way past it. redirect.pizza renews its certificates well before they expire.
No. A certificate for *.example.com covers every subdomain one level deep, such as shop.example.com, but not example.com itself and not a.shop.example.com. The root domain needs its own source hostname, which gets its own certificate. Wildcards are available from Pro.
