Quick Answer: Your website says Not Secure when the browser cannot confirm an encrypted HTTPS connection. The usual causes are a missing or expired SSL certificate, a certificate that does not match your domain, mixed content (images or scripts still loading over HTTP), or a site that never redirects visitors from HTTP to HTTPS. Most of these are fixable in under an hour.
You type in your own web address and there it is. A gray “Not Secure” label, a broken padlock, or worse, a full red warning page telling visitors your site might steal their information.
For a business, that message does real damage. Customers hesitate to fill out contact forms, shoppers abandon checkout, and some people simply hit the back button. The good news is that the warning almost always points to a specific, identifiable technical problem.
This guide walks through what the warning actually means, the seven most common causes, how to diagnose which one you have, and how to fix it for good. We also cover two big 2026 changes that make this topic more urgent than ever.
Short answer: “Not Secure” means the connection between the visitor’s browser and your website is not encrypted, or the browser cannot verify the encryption is trustworthy. Data sent through the page, such as names, emails or passwords, could potentially be read or altered in transit.
A few terms are worth defining clearly:
Browsers like Google Chrome, Mozilla Firefox, Apple Safari and Microsoft Edge all check for a valid certificate on every page load. If anything in that chain fails, they warn the visitor.
Short answer: A gray “Not Secure” label in the address bar usually means the site has no HTTPS at all or has mixed content. A full red warning page means HTTPS exists but the certificate is broken, expired or mismatched.
| What visitors see | What it usually means | Severity |
|---|---|---|
| Gray “Not Secure” text in the address bar | Page loads over plain HTTP | Moderate |
| Padlock with a warning or info icon | HTTPS page loading some HTTP content (mixed content) | Moderate |
| Full page warning: “Your connection is not private” | Expired, invalid or mismatched certificate | High |
| Error code such as NET::ERR_CERT_DATE_INVALID | Certificate expired or device clock is wrong | High |
| Error code such as NET::ERR_CERT_COMMON_NAME_INVALID | Certificate does not cover this exact domain name | High |
Knowing which version you see cuts your troubleshooting time in half.
This is the most basic cause. If your site was never set up with a certificate, every page loads over HTTP and browsers flag it. It is common on older sites, sites moved between hosts, and sites built quickly on a new domain.
Certificates do not last forever. When one expires, browsers immediately show a full warning page. This has become a bigger risk in 2026, which we explain in detail below.
A certificate issued for example.com may not cover www.example.com, shop.example.com or a new domain you switched to. Browsers treat a name mismatch as a serious red flag because it is a classic sign of impersonation.
Your site has a valid certificate, but some images, scripts, fonts or embedded files are still requested through old http:// links. This is extremely common after a site moves to HTTPS, because older posts and theme settings often still contain hardcoded HTTP URLs.
You may have a working certificate, yet visitors who type your address without “https” or click an old link still land on the insecure HTTP version. Without a permanent (301) redirect, both versions stay live.
Certificates rely on a chain of trust back to the Certificate Authority. If the intermediate certificate is missing from the server setup, some browsers and mobile devices will reject the connection even though your main certificate is fine.
Sometimes the website is fine. An incorrect date or time on the visitor’s computer, outdated browser software, aggressive antivirus HTTPS scanning, or a public WiFi login page can all trigger certificate errors. If only one person reports the warning, check this first.
Two industry changes have made SSL problems more visible and more frequent this year.
In April 2025, the CA/Browser Forum approved Ballot SC-081v3, a phased schedule that cuts the maximum lifespan of publicly trusted TLS certificates from 398 days down to 47 days by March 15, 2029. The schedule looks like this: webhostservers
| Effective date | Maximum certificate validity | Approximate renewals per year |
|---|---|---|
| Before March 15, 2026 | 398 days | About 1 |
| March 15, 2026 | 200 days | About 2 |
| March 15, 2027 | 100 days | About 4 |
| March 15, 2029 | 47 days | About 7 to 8 |
The rule applies to every certificate type, including DV, OV and EV. Our take: if you renew a paid certificate by hand once a year, that routine no longer works. Automated renewal is quickly shifting from a nice extra to a basic requirement. sslinsights
Google announced in October 2025 that Chrome would turn on “Always Use Secure Connections” by default starting with Chrome 154 in October 2026, with Chrome asking for permission before a first visit to any public site that does not support HTTPS. Google’s reasoning is that HTTPS adoption has leveled off at roughly 95 to 99 percent of public sites, and attackers can exploit insecure HTTP connections to redirect users to malicious pages. redsiftthenote
In plain terms, an HTTP only website is now a much harder sell. A visitor’s first impression may be a warning screen instead of your homepage.
Short answer: Click the icon to the left of your web address, view the certificate details, then run your domain through a free SSL checker. Together these tell you whether the problem is a missing certificate, an expiry, a name mismatch or mixed content.
Follow these steps in order:
Most reputable hosts now include a free certificate from Let’s Encrypt or AutoSSL through cPanel. Check your hosting control panel for an SSL/TLS section and enable it for every domain and subdomain you use. Paid OV or EV certificates are only worth it if you specifically need organization validation for compliance or corporate policy.
Given the shorter lifespans above, automation is the single most important fix. Free certificates through Let’s Encrypt and AutoSSL renew on their own when configured correctly. If you use a paid certificate, ask your provider about ACME based automated renewal, and set a calendar reminder 30 days before expiry as a backup.
Your certificate should include both yourdomain.com and www.yourdomain.com, plus any subdomains you actively use. If you recently changed domains, issue a new certificate for the new name.
Set a permanent redirect so every HTTP request moves to HTTPS. In cPanel, this is often a simple “Force HTTPS Redirect” toggle under Domains. On Apache servers it can also be done in the .htaccess file. Once everything works reliably, consider enabling HSTS, which tells browsers to only ever connect to your domain over HTTPS.
For WordPress sites, this usually means three steps:
A plugin like Really Simple SSL can patch many mixed content issues automatically, but fixing the actual links is the cleaner long term solution.
If SSL Labs reports “chain issues” or “incomplete,” reinstall the certificate along with the intermediate (CA bundle) file your provider supplies. Hosts that issue certificates automatically normally handle this for you.
If you use Cloudflare or another CDN, its SSL mode must match your server setup. A “Flexible” mode on Cloudflare, for example, encrypts the visitor to Cloudflare leg but not Cloudflare to your server, which can cause redirect loops or inconsistent results.
Short answer: Yes, indirectly and directly. Google confirmed HTTPS as a lightweight ranking signal back in 2014, but the bigger impact is behavioral. Warnings drive visitors away quickly, reduce conversions, and can stop users from ever reaching your content.
Beyond rankings, a security warning undermines trust signals that matter for local businesses and online stores. It can also cause analytics gaps, because referral data from HTTPS sites is often stripped when passing to HTTP pages.
Most SSL fixes are straightforward, but bring in your hosting provider or a developer if:
This usually happens because of mixed content, meaning some images, scripts or files on the page still load through HTTP links. It can also happen if visitors land on the HTTP version because no redirect exists, or if the certificate does not cover the www version of your domain.
Certificates issued on or after March 15, 2026 can be valid for a maximum of 200 days. That drops to 100 days in March 2027 and 47 days in March 2029. Free Let’s Encrypt certificates have always been shorter and renew automatically when properly configured.
Yes, for encryption purposes. Free certificates from Let’s Encrypt use the same encryption strength as paid ones. Paid certificates mainly add organization validation, warranties and dedicated support. For most small business websites and blogs, a free certificate with automatic renewal is completely sufficient.
It can. HTTPS is a confirmed lightweight Google ranking signal, and warning screens push visitors away before they engage with your content. Higher bounce rates and lost conversions hurt your business results even more than the direct ranking effect.
If most visitors see no warning, the problem is probably on that person’s device. An incorrect system date, an outdated browser, antivirus software that scans HTTPS traffic, or a public WiFi login page can all trigger certificate errors on an otherwise healthy website.
Set both site URLs in Settings to start with https, then back up your database and use a search and replace tool to update old http links. Check theme settings and page builder elements for hardcoded links. Chrome DevTools will show any remaining files causing the problem.
TLS is the modern, more secure successor to SSL. All older SSL versions are now deprecated and considered unsafe. The industry still uses the term “SSL certificate” out of habit, but the certificates installed on websites today actually enable TLS encryption.
No. Chrome shows a warning that visitors can choose to bypass, and it avoids repeatedly warning about the same site. Still, many people will not click past a security warning, so an HTTP only site is likely to lose a meaningful share of first time visitors.
A “Not Secure” warning is not a mystery. It is your browser telling you exactly which piece of the HTTPS puzzle is missing, whether that is the certificate itself, its renewal, its domain coverage, a redirect, or a handful of old HTTP links. With certificate lifespans shrinking and Chrome now warning before visitors reach HTTP sites, getting this right has never mattered more.
Every hosting plan at Web Host Servers includes a free SSL certificate along with daily malware scanning and automated backups, and our team is available around the clock if you need a hand tracking down a stubborn warning. If your current site keeps showing security errors, reach out through our contact page or call +1 (213) 293-0540 and we’ll be happy to take a look.