If your website shows “Not Secure” after changing hosting, the most common reason is that your SSL certificate has not been installed or configured correctly on the new server. DNS changes, incorrect HTTPS settings, expired certificates, or mixed content can also cause the warning.
The good news is that this problem is usually fixable. In most cases, you don’t need to change your domain or rebuild your website. You simply need to check your SSL, DNS, and HTTPS configuration.
What Does “Not Secure” Mean?
When a browser displays “Not Secure” next to your website address, it generally means the connection is not properly protected by HTTPS.
A secure website normally uses an address such as:
https://example.com
Instead of:
http://example.com
HTTPS uses an SSL/TLS certificate to encrypt information transferred between visitors and your website.
This is particularly important for websites that handle login details, contact forms, customer information, or payments.
Why Does Hosting Migration Affect SSL?
Your SSL certificate is connected to your website’s domain and server configuration.
When you change hosting providers, your website moves to a different server. The new server may not automatically have the same SSL certificate or HTTPS configuration that existed on your previous hosting account.
For example, your old hosting provider may have automatically installed a free SSL certificate. After moving to a new host, you may need to activate or install SSL again.
That’s why a website can work normally after migration while still showing a security warning.
7 Reasons Your Website Shows “Not Secure” After Changing Hosting
1. SSL Has Not Been Installed
The most common reason is that the new hosting account doesn’t have an active SSL certificate.
Many hosting companies provide free SSL certificates, but you may still need to activate them from the hosting control panel.
Check whether SSL is enabled for both:
- example.com
- www.example.com
2. DNS Is Still Pointing to the Old Server
After changing hosting, your domain’s DNS records or nameservers need to point to the new hosting server.
If the DNS configuration hasn’t updated correctly, visitors may still reach the old server while other visitors reach the new one.
This can create inconsistent SSL behavior during migration.
3. The SSL Certificate Doesn’t Cover Your Domain
An SSL certificate needs to match the domain visitors are accessing.
For example, if the certificate covers:
example.com
but the www version isn’t properly covered or configured, you may encounter HTTPS problems.
Make sure all important versions of your domain are correctly configured.
4. HTTPS Is Not Enabled
Installing an SSL certificate isn’t always enough.
Your website also needs to use HTTPS correctly.
After SSL installation, test your website using:
https://yourdomain.com
If the HTTPS version works but the HTTP version remains accessible, you may need to configure an HTTP-to-HTTPS redirect.
5. Your WordPress URL Still Uses HTTP
If you’re using WordPress, check the WordPress Address (URL) and Site Address (URL).
They should normally use HTTPS:
https://yourdomain.com
If your WordPress installation still uses HTTP, the site may not behave as expected after migration.
6. Mixed Content Is Blocking Secure Resources
Sometimes the SSL certificate is working, but the browser still reports security issues because some website resources are being loaded over HTTP.
These resources can include:
- Images
- CSS files
- JavaScript files
- Fonts
- Videos
- External scripts
For example, your page may load over HTTPS while an image is loaded from:
http://example.com/image.jpg
This is called mixed content.
7. The SSL Certificate Has Expired or Failed to Renew
SSL certificates have expiration dates.
If automatic renewal didn’t work after the migration, your certificate may have expired.
Check the certificate’s status and expiration date through your hosting control panel or browser security information.
How to Fix “Not Secure” After Changing Hosting
Follow these steps in order.
Step 1: Check Your Website With HTTPS
Open your website using:
https://yourdomain.com
If it doesn’t load correctly, continue with the next steps.
Step 2: Check SSL in Your Hosting Account
Log in to your new hosting control panel and look for an option such as:
- SSL
- SSL/TLS
- Security
- Let’s Encrypt
- Free SSL
Confirm that an active certificate exists for your domain.
Step 3: Check Your DNS Settings
Make sure your domain points to the correct new hosting server.
If you recently changed nameservers, DNS propagation may still be taking place.
Avoid repeatedly changing DNS records while the migration is in progress because this can make troubleshooting more difficult.
Step 4: Force HTTPS
Once SSL is working, configure your website to redirect HTTP traffic to HTTPS.
For WordPress websites, this can usually be configured through the hosting platform, WordPress settings, or an appropriate HTTPS/redirect configuration.
Step 5: Check WordPress URLs
Go to your WordPress settings and make sure the website URL uses HTTPS.
For example:
https://yourdomain.com
not:
http://yourdomain.com
Step 6: Find Mixed Content
If HTTPS works but your browser still reports a security problem, check whether any resources are being loaded through HTTP.
Update those URLs to HTTPS where appropriate.
Step 7: Clear Cache
After fixing SSL and HTTPS settings, clear:
- WordPress cache
- Hosting cache
- CDN cache
- Browser cache
Then test the website again.
How to Check Whether Your SSL Certificate Is Working
You can check your website from multiple browsers and devices.
Look for the padlock or secure connection indicator in the browser’s address bar.
Also test both:
https://yourdomain.com
and
https://www.yourdomain.com
If one works while the other produces an SSL warning, your certificate or domain configuration may need additional attention.
What If HTTPS Works but Some Pages Still Show “Not Secure”?
If your homepage is secure but certain pages show warnings, the problem may be mixed content.
This can happen when an old HTTP URL remains inside your website database, theme, plugin, image URL, or custom code.
Check the affected page for resources that still use HTTP.
Replacing those URLs with HTTPS can resolve the problem.
You should also check whether an outdated plugin, theme, or external resource is causing the issue.
Do You Need to Buy SSL Again After Changing Hosting?
Not necessarily.
Many hosting providers offer free SSL certificates, so you may not need to purchase another certificate.
If you previously used a paid SSL certificate, you may be able to install the existing certificate on the new server, depending on the certificate type and provider.
Before buying another certificate, check what SSL options your new hosting provider offers.
How to Prevent SSL Problems During Future Hosting Migrations
A little preparation can prevent most HTTPS problems.
Before moving your website:
- Check your current SSL configuration.
- Back up your website.
- Back up important DNS records.
- Check where your domain’s DNS is managed.
- Activate SSL on the new server.
- Test the new hosting environment.
- Update DNS only when the new server is ready.
- Test HTTPS after the DNS change.
- Check for mixed content.
- Keep the old hosting account active until everything works correctly.
Final Checklist
Before considering your hosting migration complete, make sure:
- [ ] SSL is active on the new hosting account.
- [ ] Your domain points to the correct server.
- [ ] HTTPS loads correctly.
- [ ] HTTP redirects to HTTPS.
- [ ] Both www and non-www versions work correctly.
- [ ] WordPress URLs use HTTPS.
- [ ] No important resources are loaded through HTTP.
- [ ] Your SSL certificate is valid and not expired.
- [ ] Website and browser caches have been cleared.
- [ ] Important pages have been tested.
Conclusion
Seeing “Not Secure” after changing hosting doesn’t necessarily mean your website has been hacked or that you need a new domain. In many cases, the problem is simply an SSL certificate, DNS configuration, HTTPS redirect, or mixed-content issue.
Start by checking whether SSL is active on your new hosting account. Then verify your DNS, HTTPS configuration, WordPress URLs, and website resources.
If you check these areas systematically, you can usually identify the cause and restore a secure HTTPS connection without rebuilding your website.