Why Does My Website Say Not Secure? What It Means and How to Fix It
If you have noticed the words “Not secure” in your browser when visiting your business website, it is something worth investigating. It does not automatically mean your website has been hacked, but it can mean the connection between your visitor and your website is not being properly protected.
For a small business, that warning can also create a trust problem. Imagine a potential customer visiting your website to request a quote, make a booking or complete a contact form. Seeing a security warning could make them think twice about entering their details or even continuing to use the website.
Fortunately, the reason a website says not secure is often fairly straightforward to identify. In many cases, it involves HTTPS, an SSL/TLS certificate or part of the website still loading through an insecure connection.
Quick Answer
Why does my website say not secure? A browser will normally show a security warning when it cannot establish a properly secured HTTPS connection with your website. This can happen because your site is still using HTTP, its SSL/TLS certificate is missing, expired or incorrectly configured, or because some website resources are being loaded insecurely.
HTTPS encrypts information travelling between a visitor’s browser and your website. If your business website displays a security warning, it is worth getting the cause checked rather than ignoring it, especially if your site has contact forms, login areas, bookings or other features where visitors enter information.
What Does “Not Secure” Actually Mean?
A “Not secure” warning usually relates to the connection between the visitor’s browser and the website. Google Chrome explains that when a site does not use a private connection, information sent to or received from the website may potentially be viewed or changed by someone else.
This is different from saying the website itself definitely contains malware or has been hacked. Browsers use different types of warnings for different security problems. A connection warning is primarily telling the visitor that the browser cannot confirm a properly protected connection to that website.
For a business owner, the important point is that visitors may not understand the technical difference. They may simply see the words “Not secure” and decide they do not trust the website.
What Is the Difference Between HTTP and HTTPS?
One of the easiest things to check is the beginning of your website address.
An older, unsecured address may begin with:
http://
A website using a secured connection normally begins with:
https://
The extra “s” stands for secure. HTTPS uses encryption to protect information while it travels between a visitor’s browser and the website server.
For example, imagine somebody visits an accountant’s website and sends an enquiry through a contact form. HTTPS helps protect the information while it travels across the internet. Encryption makes that information much harder for an unauthorised third party to read or alter while it is in transit.
HTTPS does not make a website completely immune to hacking, malware or every other security problem. It deals with an important part of website security: protecting the connection between the visitor and the website.
What Is an SSL/TLS Certificate?
To use HTTPS correctly, a website needs a valid digital certificate. You will often hear this called an SSL certificate, although modern secure web connections use TLS technology.
The certificate helps the browser establish an encrypted connection and confirm that it is communicating with the website covered by that certificate.
Many hosting companies provide certificates as part of their hosting service, and some automatically install and renew them. However, having a certificate available through your hosting account does not always mean the whole website has been configured correctly to use HTTPS.
A certificate can exist while a website still has problems. The certificate might have expired, the domain may not be correctly covered, redirects may be wrong or some resources on a page may still be using insecure HTTP addresses.
Common Reasons Your Website Says Not Secure
There is no single cause that applies to every website. The warning needs to be investigated to find out what is happening on your particular site.
1. Your Website Is Still Using HTTP
The simplest explanation is that your website has never been moved fully to HTTPS. If visitors are reaching an HTTP version of the site, their browser may warn them that the connection is not secure.
This can happen with older business websites that were created before HTTPS became standard practice. It can also happen when a website has been moved between hosting companies without its security settings being configured correctly afterwards.
2. The SSL/TLS Certificate Has Expired
Certificates have a validity period and need to be renewed. Many modern hosting systems handle renewal automatically, but automated renewal can sometimes fail because of hosting, DNS or configuration problems.
If the certificate is no longer valid, visitors may receive a browser warning. Depending on the problem, they may see a much stronger message such as “Your connection is not private” rather than simply “Not secure”.
3. The Certificate Does Not Match the Website Address
A certificate needs to cover the hostname visitors are using. Problems can occur if the certificate is set up for one version of the domain but the visitor is being sent to another version that is not covered.
Subdomains can create similar issues. If your business uses different subdomains for customer areas, booking systems or other services, each relevant hostname needs the appropriate HTTPS configuration.
4. The SSL/TLS Certificate Has Not Been Installed Correctly
Sometimes a certificate has been purchased or issued but the website or server has not been configured correctly to use it.
This can happen after moving a website, changing hosting settings, altering DNS records or making server changes. The certificate itself may be perfectly valid, but visitors can still experience errors if the configuration around it is wrong.
5. Your Website Has Mixed Content
A website can load its main page using HTTPS while still requesting some resources through old HTTP addresses. This is commonly known as mixed content.
Those resources could include images, stylesheets, scripts, fonts or other files. This often appears after an older website has been converted from HTTP to HTTPS but some old addresses remain within the website.
Mixed content should be corrected rather than assuming that installing a certificate has finished the job.
6. Your Website Redirects Are Incorrect
Once HTTPS is working, visitors who use the old HTTP address should normally be redirected to the HTTPS version.
If redirects have not been configured correctly, people may still be able to reach an insecure version of the website. You can therefore end up with different visitors having different experiences depending on which address or old link they use.
7. A Recent Website or Hosting Change Has Caused a Problem
If the warning has suddenly appeared on a website that was previously secure, think about what has changed recently.
Has the website moved to a different hosting company? Have the domain’s DNS settings changed? Has a staging website recently been made live? Has a CDN or security service been added? Has the site’s URL configuration been changed?
These changes do not automatically cause security problems, but they can help narrow down where to investigate.
Warning
If visitors see a security warning on pages where they are expected to enter passwords, contact details, payment information or other personal information, do not simply ignore it. Find out why the warning is appearing and correct the underlying problem.
If you are unsure what has caused it, ask your hosting provider or the person responsible for maintaining your website to investigate it.
Why the Warning Matters to a Small Business
A security warning is not just a technical issue. It can affect how potential customers feel about your business.
Imagine somebody finds a local electrician through Google and visits the company’s website. They are ready to request a quote, but their browser tells them the connection is not secure. The visitor does not know whether the problem is minor or serious. They only know that their browser is warning them.
The same applies to a beauty salon asking customers to book online, an accountant collecting enquiry details or a cleaning company using a quote request form. Customers need to feel comfortable using the website.
A professional-looking design cannot completely overcome a browser security warning. If the browser itself raises concerns, some visitors may leave rather than investigate what the warning technically means.
Does Not Secure Mean My Website Has Been Hacked?
No. A “Not secure” message does not, by itself, prove that your website has been hacked.
The warning may simply mean that the browser has not established a private HTTPS connection. This could be because the site uses HTTP or because there is a problem with its certificate or HTTPS configuration.
A hacked website is a different issue. Signs of a compromised website can include unexpected pages, strange redirects, unfamiliar administrator accounts, changed files, spam content, malicious code or security warnings relating specifically to malware or phishing.
That distinction matters because you need to solve the right problem. Installing an SSL/TLS certificate does not remove malware from a hacked website, while cleaning malware will not fix a missing or incorrectly configured certificate.
How Do You Fix a Not Secure Website?
The exact fix depends on the cause. If you are comfortable managing your hosting and website settings, there are several checks you can make. If not, your hosting company or website maintenance provider should be able to investigate them.
Check Whether Your Website Uses HTTPS
Open your website and look at the full address. Check whether it begins with HTTPS and whether your browser shows any connection warnings.
It is also sensible to check more than the homepage. Visit your contact page, important service pages, login areas and any pages containing forms.
Check the Certificate
Your hosting control panel may show whether a certificate is active for your domain. You can also use the browser’s site information controls to view information about the connection.
If the certificate has expired or is not valid for the address being used, that needs to be corrected.
Check Both Versions of Your Domain
If your website can be reached using both the www and non-www versions of your domain, make sure the intended versions are properly handled and visitors are redirected consistently.
Also check any subdomains that form part of your normal website or customer journey.
Look for Mixed Content
If HTTPS appears to be installed but problems remain, old HTTP resources may still be loading within the site.
These references may need to be changed to secure HTTPS addresses. With a WordPress website, old URLs can sometimes remain in the database, theme settings, page builder content, plugins or custom code after an HTTPS migration.
Set Up the Correct Redirects
Visitors using an old HTTP link should normally be sent automatically to the HTTPS version of the page.
This needs to be configured carefully. Incorrect redirects can create loops, broken pages or send visitors to the wrong destination, so it is worth getting professional help if you are not comfortable changing server or website settings.
Test the Website Afterwards
Do not assume the problem is solved because the homepage appears correctly.
Check important pages and test the website on more than one device or browser where practical. Test forms and other important features too, particularly if changes were made to URLs, redirects, hosting or website settings.
Expert Insight From Daren Ward
Expert Insight From Daren Ward
Daren Ward – Founder, A to Z Website Solutions
From my experience working with business websites, I would not treat a “Not secure” warning as something to leave until later. Even when the cause is relatively simple, your customers do not know that. They only see their browser warning them about your website.
I would normally start by checking the SSL/TLS certificate, HTTPS setup, redirects and whether the site is loading any old HTTP resources. I would also look at whether anything has changed recently, particularly hosting, DNS settings, website migrations or domain configuration.
Once the problem is fixed, I would test the website rather than just checking the homepage and assuming everything is fine. Contact forms, important service pages, login areas and other key parts of the site should be checked too.
This is also why ongoing website maintenance matters. Backups, updates, security checks and testing can help you spot technical problems before they are left unnoticed for long periods.
Action Checklist
What to Check If Your Website Says Not Secure
- Open your website and check whether the address begins with HTTPS.
- Use your browser’s site information controls to check the connection status.
- Check whether your SSL/TLS certificate is active and valid.
- Check both the www and non-www versions of your domain where relevant.
- Check important subdomains if your business uses them.
- Look for old HTTP resources causing mixed content problems.
- Make sure HTTP visitors are correctly redirected to HTTPS.
- Think about any recent hosting, DNS or website changes.
- Test contact forms and other important website features after making changes.
- Ask your hosting company or website maintenance provider for help if you are unsure what is causing the warning.
Frequently Asked Questions
Why does my website say not secure even though I have an SSL certificate?
Having a certificate does not guarantee that every part of the HTTPS setup is correct. The certificate could be expired, incorrectly configured or not valid for the hostname being used. Your website could also contain insecure HTTP resources or have incorrect redirects. The actual connection needs to be checked to identify the cause.
Can people still visit a website that says not secure?
Sometimes they can, depending on the type of warning and their browser settings. However, visitors may be warned that the connection is not private or secure. A stronger certificate error may result in a full-page warning that makes proceeding much more difficult and may discourage visitors from continuing.
Does HTTPS mean my website cannot be hacked?
No. HTTPS protects information while it travels between the browser and website, but it does not make the website immune to every attack. Website software, passwords, hosting security, plugins, themes, user accounts, backups and maintenance can all form part of a wider security approach.
Is SSL the same as HTTPS?
They are closely related but are not exactly the same thing. HTTPS is the secure version of HTTP used to transfer web content. A digital certificate and TLS are used as part of establishing that secure connection. People still commonly use the phrase “SSL certificate” even though modern secure connections use TLS.
Can an expired SSL certificate make my website show a warning?
Yes. An expired certificate can cause browsers to display a security or privacy warning because the certificate is no longer within its valid period. If automatic renewal was expected, the reason it failed should also be investigated so the problem does not simply happen again.
What is mixed content on a website?
Mixed content occurs when a page is loaded through HTTPS but some resources on that page are requested through insecure HTTP connections. These could include images, scripts, stylesheets or other files. Old HTTP references should be identified and corrected as part of properly moving a website to HTTPS.
Should every business website use HTTPS?
Yes, a modern public business website should normally use HTTPS. It protects data in transit and allows browsers to establish a private connection with the website. This matters even if you do not sell products online because ordinary business websites often have contact forms, booking features, login areas or other ways for visitors to submit information.
Why has my website suddenly become not secure?
If the warning has appeared suddenly, check whether the certificate has expired or whether something recently changed. A website migration, hosting change, DNS change, certificate renewal failure or configuration change could be involved. Finding out what changed shortly before the problem appeared can help narrow down the cause.
Can my hosting company fix a not secure warning?
Possibly. If the problem relates to the certificate, hosting configuration or server settings, your hosting provider may be able to help. If the problem is inside the website itself, such as old HTTP URLs or website configuration, you may need help from whoever maintains your website.
How often should I check my website security?
Website security should not be treated as a one-time job. Regular maintenance can include software updates, backups, security checks, form testing and checking that important parts of the website continue to work correctly. Automated systems are useful, but they should not replace checking that the website is actually working as expected.
Summary
If you have been wondering, “Why does my website say not secure?”, the warning usually means the visitor’s browser cannot establish the secure HTTPS connection it expects.
The cause could be as simple as the website still using HTTP, but it could also involve an expired or incorrectly configured SSL/TLS certificate, mixed content, redirects or a recent hosting or domain change.
The warning does not automatically mean your website has been hacked. However, it should still be investigated because HTTPS helps protect information travelling between your visitors and your website, and browser warnings can also reduce customer confidence.
Find the cause, correct it and then test the important parts of the website. If you are not comfortable dealing with certificates, redirects, hosting or website settings yourself, ask your hosting provider or website maintenance company to investigate.
Would You Like Help With Your Website?
Keeping a business website running properly involves more than updating the words and pictures. Security, backups, WordPress updates, plugin updates and regular checks all play a part in keeping the site working as expected.
If you would prefer somebody to help look after the technical side, you can find out more about our WordPress Maintenance service. It provides ongoing support for updates, security, stability and the day-to-day operation of your WordPress website.
Key Takeaways
- A “Not secure” warning usually relates to the connection between a visitor’s browser and your website.
- It does not automatically mean that your website has been hacked.
- A modern business website should normally use HTTPS.
- An expired, missing or incorrectly configured SSL/TLS certificate can cause security warnings.
- Mixed content can cause problems even when HTTPS has already been installed.
- Incorrect redirects can leave visitors reaching an insecure HTTP version of the website.
- Browser security warnings can affect customer confidence, especially around forms, bookings and logins.
- After fixing the problem, test important pages and website features rather than checking only the homepage.