Website not secure warning: causes and fix
Your visitors see 'Not secure' on your site. This is what the warning means, what the four causes are and how to fix it yourself, even without technical knowledge.
Team Netslim 9 Nov 2026 7 min read
A customer calls: “It says ‘Not secure’ on your website, has it been hacked?” Usually not. But the website not secure warning in the browser does cost you visitors, because few people fill in a contact form on a site that calls itself unsafe.
The good news: the cause is almost always one of four things, and you can quickly see which one it is. Below you can read what an SSL certificate is, why the browser complains and how to fix it. You don't need to be a developer.
What does the website not secure warning mean?
For every site, the browser checks whether the connection between the visitor and the server is encrypted. If it isn't, or if something is wrong with the proof of that, the visitor gets a warning. It looks different depending on the situation:
- “Not secure” in the address bar. The page was loaded without encryption (http instead of https). This is the mildest variant.
- A full-screen warning. For example “Your connection is not private” in Chrome, or “Warning: potential security risk ahead” in Firefox. This means there is a problem with the certificate itself, and the visitor has to click through on purpose.
- No padlock, or a padlock with an exclamation mark. The page is https, but part of the content is not. This is called mixed content.
Important to understand: the warning says something about the connection, not about the content of your site. A hacked site can have a perfectly good padlock, and a harmless site without a certificate still gets the warning.
What is an SSL certificate?
An SSL certificate is a digital proof that belongs to your domain name. It does two things. It makes sure that what your visitor enters (a password, an address, a message) travels over the internet encrypted. And it proves that the server the visitor is talking to really belongs to your domain, and not to someone pretending to be you.

Technically, the current technology is called TLS, but everyone still says SSL, so we do too. The certificate sits on the server, not in your WordPress theme or your website builder. You can recognise a site with a certificate by https:// at the start of the address.
Two things people often don't know. A certificate has a term and so must be renewed. And it is tied to specific domain names: jouwbedrijf.nl and www.jouwbedrijf.nl count as two different addresses to the browser.
The four causes of a warning
1. There is no certificate
Your site still runs on http. This happens with older sites, with hosting where SSL is not switched on, or with a new domain that has just been connected. The browser then shows “Not secure”, especially as soon as there is a form or login field on the page.
2. The certificate has expired
This is the classic. The certificate worked fine for months, and one morning everyone gets a full-screen warning. Usually the automatic renewal failed, or automatic renewal was never set up. Sometimes it is caused by moving the site, where the certificate was not moved along.
3. The certificate does not match the address
The certificate was issued for jouwbedrijf.nl, but your visitor types www.jouwbedrijf.nl. Or the other way around. A subdomain such as shop.jouwbedrijf.nl also falls outside a certificate that only applies to the main domain. The browser sees a name that is not on the certificate and raises the alarm.
4. Mixed content
The certificate is fine and the page loads over https, but there is still an image, script or font that is fetched over http. The browser rightly finds that messy: the page is only half secure. This often happens after switching to https. Old images in your posts, a hardcoded link in your theme or an embedded element from an external service are the usual suspects.
There is also a fifth cause, which is not your fault: the date or time on the visitor's device is wrong. A laptop that is years behind sees every certificate as invalid. Only getting a complaint from one person? Then first ask whether their clock is right.
How to find out which cause it is
Start with the quickest check: go to your site yourself, try both the version with and without www, and click the padlock or the warning on the left of the address bar. It shows whether the certificate is valid and until when.
Want to skip the puzzling? Run the free website check. It tests your SSL, your security headers and whether your site runs properly on https, among other things. You get an overview in plain language, without having to install anything.
A quick guide for yourself:
- Full warning screen saying “expired”? Then the certificate has expired.
- Warning only on the version with or without
www? Then the name on the certificate does not match. - Just “Not secure” and
http://in the address bar? Then no certificate is in use, or your site does not redirect to https. - Page loads over https but the padlock is missing? Then it is mixed content.
How to fix the warning
Certificate missing or expired
You install or renew a certificate with the party that handles your hosting. With a Plesk hosting package, you find it in the control panel under the SSL/TLS settings of your domain, and you can usually request a free certificate in a few clicks. Allow a few minutes, and after that it can take a little while before it is visible everywhere.
Make sure automatic renewal is turned on. That saves you a phone call from that customer a year from now. With Netslim web hosting, free SSL is enabled by default, so you do not have to think about the certificate yourself. Is your site with a provider that has no solution for this? Then moving is often faster than continuing to fight it.
Name does not match
Make sure the certificate covers both the main domain and the wwwvariant (and any subdomains you use). Then choose one preferred address and permanently redirect the other version to it. This is also better for your visibility in search, because otherwise Google sees two versions of your site.
No redirect to https
Even with a valid certificate, someone can still end up on the http version, for example through an old link or bookmark. So turn on a permanent redirect (301) from http to https. In Plesk, this is a checkbox in the hosting settings of your domain. In WordPress, this usually works automatically once you change the addresses.
Mixed content in WordPress
First make a backup, because you are going to replace things. How often to make one and where to store it is covered in this article about backups. Then:
- Go to Settings, General, and set both the WordPress address and the site address to
https://. - Replace old
http://jouwbedrijf.nllinks in your database with the https version. You do this with a search-and-replace tool for WordPress. Be careful with manual cutting and pasting in the database: an error in stored, serialized data can break things. - Check your theme, widgets, menus and any page builder blocks for links that still start with
http://. - Open the page, press F12 and look at the Console tab. The browser lists exactly which files still load over http.
Do you find an image or script from an external service that is only reachable over http? Then that service has a problem of its own. Replace the element with an alternative.
Does your site run on WordPress and do you want less of this kind of maintenance? Take a look at WordPress hosting, where updates and SSL are already taken care of.
If the warning comes back or something else is going on
If the problem comes back after a few weeks or months, there is almost always something wrong with the renewal. A certificate that was installed manually and does not renew by itself is the most common reason.
Besides the warning, do you also see strange pages, redirects to sites you do not know, or spam in your search results? Then there may be more going on than a certificate. Read what to do in the first 24 hours if your site is hacked.
Do you have a new domain that you are not using yet? Even then, a visitor should not see a warning. How that works is explained in the article about a domain that is parked automatically with SSL.
What to do now
- Open your site with and without
www, and see what the browser says. - Run the free website check and note what is red.
- Fix the certificate (install, renew or add the name) and turn on the redirect to https.
- Then deal with any mixed content, with a backup at hand.
- Test again, also on your phone, and turn on automatic renewal so it does not happen again.
Can't work it out, or would you rather not do this yourself? Feel free to contact us. A certificate and a redirect are quickly sorted for us, and then you can get back to work.
Frequently asked questions
Is my website hacked if it says 'Not secure'?
Usually not. The warning is about the connection, not about what is on your site. If you also see pages you do not know, strange redirects or spam in Google, a hack is possible and you need to look beyond the certificate.
Can I get an SSL certificate for free?
Yes, a standard certificate for your website does not have to cost anything. Many hosting packages include one by default and renew it automatically. Paid certificates exist for those who want extra verification of the company name, but for most small sites that is not necessary.
Do I need SSL if my site has no form or web shop?
Yes, even then. Browsers can mark any http page as 'Not secure', visitors leave because of the warning, and Google prefers an https site. It costs you nothing extra, so there is little reason to skip it.
How long does it take for the padlock to appear after installing?
Often within a few minutes, sometimes it takes longer. What you can do yourself is open the page in a private window, so the browser does not show an old version from its cache. If the warning stays, there is usually still mixed content or the redirect to https is missing.
Why do some visitors see the warning and I do not?
This can happen because the date or time on their device is wrong, because they use the address with or without www, or because their antivirus or network intercepts the connection. So test your site on several devices and both address variants.
Read also
All blogs →
Security6 min read
AI finds leaks in minutes: this is how you stay ahead of hackers
AI finds leaks in websites in hours or minutes, and AI chatbots cause data leaks themselves. What is changing and seven measures you can take now.
Security6 min read
Set up two-step verification for WordPress and email
Here is how you turn on two-step verification for your WordPress login and business email, and choose between an app and a security key. Done in about an hour.
Security6 min read
DDoS attack on your website: how to spot it and what to do
Your site is slow or shows 503 errors. Is it a DDoS attack or just busy? Here is how to tell, what to do right away and how to prevent it next time.