Guides to redirecting a domain over HTTPS
Written for people who own a domain, not for people who run servers. These cover the things that actually get you stuck: the DNS record, the choice between a permanent and a temporary redirect, and the certificate warning that appears before a redirect ever runs.
How to redirect a domain to another domain over HTTPS
The whole procedure end to end — what you need before you start, the single DNS record, choosing the destination, and how to check the redirect actually works.
301 vs 302 redirects: which should you use?
What the two status codes actually mean, how browsers and search engines cache them, and why using a 302 for a permanent move quietly costs you.
How to point your domain’s DNS at HTTPSredirect
Where the setting lives at six common registrars, which existing records to clear out first, how long the change takes, and three easy ways to check it worked.
Why you see “Your connection is not private” when redirecting
The handshake happens before the redirect does, so a domain that only forwards traffic still needs a certificate in its own name. What the warning means and how to clear it.
Set up your first redirect
The free plan covers one domain, certificate included. No credit card required.
Get started free