If your site shows a “Not Secure” warning, the issue is usually a certificate, DNS, or redirect problem rather than a broken website.
This guide explains how to fix SSL on Hostinger and pinpoint the exact cause fast.
What SSL does on a Hostinger website
SSL, or Secure Sockets Layer, encrypts traffic between a visitor’s browser and your server.
On modern sites, this is typically delivered through TLS certificates, but the term SSL is still widely used in hosting dashboards and tutorials.
On Hostinger, SSL matters for three main reasons:
- It protects login forms, checkout pages, and contact submissions.
- It helps browsers trust your domain and remove security warnings.
- It supports SEO, since Google uses HTTPS as a ranking signal.
Hostinger usually provides free SSL through Let’s Encrypt on supported hosting plans, but a certificate can fail to activate if DNS or site configuration is not aligned.
Check whether SSL is active in Hostinger
Before changing settings, confirm the certificate status in your Hostinger account.
In hPanel, open the website management area and look for the SSL section or SSL status indicator.
- If SSL shows as active, the certificate may be installed but your site may still load non-HTTPS resources.
- If SSL shows as pending, the domain may not be pointed correctly or propagation may still be in progress.
- If SSL is unavailable, the domain may not be attached to the correct hosting plan or may not yet be fully set up.
If you recently changed nameservers, waited less than 24 to 48 hours, or migrated a site, give DNS time to propagate before assuming the certificate is broken.
Make sure the domain points to Hostinger correctly
One of the most common reasons SSL fails on Hostinger is incorrect DNS.
Let’s Encrypt must verify that the domain resolves to the correct hosting environment before it can issue a certificate.
What to verify
- Nameservers are set to Hostinger’s values if Hostinger manages DNS.
- The A record points to the correct server IP address.
- There are no conflicting CNAME or A records for the root domain.
- The domain is not accidentally pointing to an old host or parked page.
If you use Cloudflare or another DNS provider, make sure the domain is configured consistently.
A proxy setting, such as Cloudflare’s orange-cloud mode, can sometimes interfere with certificate validation during issuance.
Reissue or activate the SSL certificate
If the certificate was not installed automatically, try triggering SSL setup again from the Hostinger dashboard.
Many SSL issues are resolved by re-running the issuance process after DNS is correct.
Common steps include:
- Open your Hostinger hPanel.
- Go to the website’s SSL section.
- Select the correct domain or subdomain.
- Click the install, activate, or reissue option if available.
- Wait for the status to change from pending to active.
For domains with multiple variants, remember that example.com and www.example.com may need to be covered correctly.
A certificate can be valid for one version while the other still triggers a browser warning.
Fix the browser warning by forcing HTTPS
Even when the certificate is installed, users may still land on the HTTP version of your site.
In that case, you need to force HTTPS so all traffic uses the secure protocol.
You can usually do this in one of the following ways:
- Enable the HTTPS redirect option in Hostinger if it is available for your setup.
- Add redirect rules in your .htaccess file for Apache-based hosting.
- Use server-level or application-level redirects if your site runs on a CMS or custom stack.
A proper redirect should send all HTTP traffic to HTTPS with a 301 status code.
This helps search engines update indexed URLs and reduces duplicate content problems.
Identify mixed content issues
A valid certificate does not guarantee a fully secure page.
If your site loads images, scripts, fonts, or stylesheets over HTTP, browsers may still show a warning or a broken lock icon.
This is known as mixed content.
Where mixed content usually comes from
- Hardcoded image URLs inside posts or page builders.
- Old theme files referencing http:// links.
- External scripts, widgets, or font files loaded without HTTPS.
- Database entries created before the site moved to SSL.
To fix this, update internal links from HTTP to HTTPS, clear cache, and rescan the site.
If you use WordPress, a search-and-replace tool or a plugin designed for URL replacement can help update stored content safely.
Clear caches after SSL changes
SSL fixes often appear to fail simply because cached content is still serving old HTTP links or stale redirect responses.
Clear every relevant cache layer after making changes.
- Browser cache and cookies
- WordPress cache plugins
- Hostinger cache, if enabled
- CDN cache, such as Cloudflare
- Object cache or server-side cache if your setup uses one
After clearing cache, test the site in an incognito window and on a mobile network if possible.
This helps confirm the problem is not local to one device or one browser session.
Check for certificate mismatch or expiration
Sometimes the SSL error is caused by a certificate mismatch.
This happens when the certificate does not match the domain being visited, or when the certificate has expired and was not renewed correctly.
Look for these signs:
- The certificate is issued for a different hostname.
- The certificate is valid for the apex domain but not the www subdomain, or vice versa.
- The certificate expired after a migration, DNS change, or hosting suspension.
Hostinger’s free SSL certificates should renew automatically in normal conditions, but renewal can fail if the domain is no longer pointing to the account or if the hosting subscription is inactive.
Use WordPress settings if your site runs on WordPress
If your site is on WordPress, the WordPress Address and Site Address values must use https:// after SSL is active.
If they still use http://, the site may redirect incorrectly or generate insecure links.
Review these areas carefully:
- WordPress General Settings for site URLs
- Theme customization options that store a base URL
- Page builder templates with hardcoded HTTP assets
- SEO plugins that define canonical URLs
After updating URLs, log out and back in, then refresh the homepage, contact page, and checkout page to confirm secure loading across the site.
When to contact Hostinger support
If you have confirmed DNS, SSL activation, redirects, cache, and mixed content but the issue continues, Hostinger support can help verify the certificate issuance process from the server side.
This is especially useful after migration, domain transfer, or nameserver changes.
Provide support with:
- Your domain name
- A screenshot of the SSL status in hPanel
- The exact browser error message
- Any recent DNS or hosting changes
The more specific the error details, the faster support can determine whether the problem is on the DNS side, the certificate side, or the application side.
Quick checklist for how to fix SSL on Hostinger
- Confirm the domain points to the correct Hostinger hosting account.
- Wait for DNS propagation if nameservers were recently changed.
- Activate or reissue the SSL certificate in hPanel.
- Force HTTPS with a redirect.
- Replace mixed HTTP content with HTTPS URLs.
- Clear browser, site, and CDN caches.
- Check for domain mismatch, subdomain coverage, or expired certificates.
- Update WordPress URLs if applicable.
Following these steps in order covers the most common Hostinger SSL problems and helps you restore the secure padlock without guesswork.