Keep HTTPS Working: SSL Certificates After a Domain Change
Moving to a better domain name is worth it — but your SSL certificate doesn't move with you. Here's how to keep the padlock showing and avoid the scary browser warning on your new domain.
You picked a better domain name. You pointed it at your site. You set up redirects. Then a customer calls and says your site shows a warning that it's "not secure." That's an SSL problem, and it's one of the most common surprises when you switch domains.
Here's the short version: your SSL certificate is tied to your old domain name. It does not follow you to the new one. You need a new certificate for the new name. The good news is that for most small business sites, this takes a few minutes and costs nothing.
What the SSL certificate actually does
SSL is what puts the little padlock in the browser bar and turns http into https. It scrambles the connection between your customer's browser and your site so nobody in between can read it. Browsers now flag any site without it, and that warning scares people off before they ever see your phone number.
The key thing to understand: a certificate is issued for one specific domain name. A certificate for oldplumbingname.com only works for oldplumbingname.com. The moment customers start landing on dallasdrainpros.com, that old certificate doesn't apply, and the browser throws up a warning.
Why you get a "not secure" warning after the switch
When someone visits your new domain over https, the browser checks that the certificate matches the name in the address bar. If the names don't match — or there's no certificate for the new name yet — you get a full-page warning instead of your homepage.
This usually shows up in one of two ways:
- No certificate yet on the new domain. You connected the name but never issued a certificate for it.
- A mismatch. The server is still handing out the old domain's certificate for requests to the new name.
Either way, the fix is the same: get a valid certificate issued for the new domain name.
How to fix the SSL certificate after changing your domain name
How you do this depends on where your site is hosted. Pick the one that sounds like your setup.
If you use a website builder or managed host
Most builders — Squarespace, Wix, Shopify, GoDaddy Website Builder — handle SSL for you. When you add the new domain in your account, they issue a certificate for it automatically. It can take a few minutes to a few hours to kick in. If it hasn't after a day, look for an SSL or HTTPS setting in your domain panel and check that the new name is listed as primary.
If you're on WordPress hosting
Many hosts include free SSL through a service called Let's Encrypt. After you add the new domain, go to your hosting control panel and look for an SSL or "Let's Encrypt" tool, then request a certificate for the new name. If you moved your WordPress site as part of this, walk through moving a WordPress site to a new domain without breaking it so the site address settings match the new name too.
If someone built your site for you
Send your web person one line: "We changed our domain to NEWNAME.com — please issue an SSL certificate for it so https works." They'll know exactly what to do. This is a normal, quick job.
The order matters
SSL works best when the name already points at your site. The certificate service has to confirm you control the domain, and it does that by checking the live connection. So the smart order is:
- Point the new domain at your site. If you haven't yet, here's how to point your new domain to your current website.
- Let it start loading.
- Issue or confirm the SSL certificate for the new name.
- Set up your 301 redirects from the old domain to the new one.
One detail on redirects: your old domain needs a working certificate too, at least for a while. When someone clicks an old link, the browser briefly loads the old https address before the redirect sends them along. If the old certificate has lapsed, they can hit a warning on the way through. Keep the old one valid until traffic to it dries up.
How to check it's really working
Don't take the host's word for it. Test it yourself:
- Type https:// plus your new domain into a browser and confirm the padlock shows, with no warning.
- Try it with www and without. Both should load cleanly.
- Click an old link or type your old domain. It should redirect to the new site without a security warning in between.
- Check on your phone, not just your computer.
If you want a deeper look, Let's Encrypt explains how certificates work in plain terms on their site: letsencrypt.org/how-it-works.
A few things that trip people up
Certificates expire. Free ones often renew automatically, but if yours was set up by hand, put a reminder on your calendar. An expired certificate throws the same scary warning as having none at all.
Also, fixing SSL is one piece of a clean move, not the whole thing. The internal links inside your pages still point at the old name until you fix the links inside your site after you switch domains. Handle both and your new name will load fast, secure, and without surprises.
Weighing whether a cleaner, easier-to-say domain is worth the trouble at all? The security piece is the small part — and it's free on most hosts. Browse names for your city and trade on PixelWorks Domains, or ask us about one specific name you have in mind. It takes about a minute.