23/09/2026
33 people viewing
12 min read

What an SSL Certificate Is and Why Your Site Needs One

SSL certificate illustration: a browser with an https padlock, a security shield, and a certificate

⚡ Quick answer: An SSL certificate (strictly speaking, TLS) is a file on the server that encrypts data between the visitor’s browser and your site and proves the site is genuine rather than a phishing copy. With it, the site loads over https:// with a padlock; without it, browsers show “Not secure”, and from October 2026 Chrome will by default ask for confirmation before opening a site without HTTPS. For most sites a free Let’s Encrypt certificate, switched on in the hosting panel, is all you need.

In late 2026, a great many websites will suddenly get a red flag in the browser — and their owners will hear about it from confused customers rather than from any dashboard. The reason will be the same in almost every case: a missing or misconfigured SSL certificate.

Google has already confirmed that with Chrome 154, which becomes the default for all users in October 2026, the browser will ask for confirmation before opening any public site that does not support HTTPS. Earlier, from Chrome 147 in April 2026, this was switched on for over a billion users with Enhanced Safe Browsing. So the “this site is not secure” screen is about to be seen not by a technician in the settings menu, but by an ordinary visitor — a second before they decide not to buy from you after all.

Let’s break it down without jargon: what this certificate actually is, what it really does, how much it costs (often nothing) and how to tell when something is wrong with yours.

What an SSL certificate actually does

When a visitor fills in a form on your site — name, phone number, card details — that data travels from their device to your server through dozens of intermediate points. Without encryption, anyone along that path, from the admin of a café’s public Wi-Fi to an internet provider, can read it in plain text.

An SSL certificate (technically TLS now, but the old name stuck) does two things. It encrypts that stream, turning the data into an unreadable set of characters for everyone except the destination server. And it confirms that the site the visitor opened really is yours, not a phishing copy that stole your design and logo.

Technically, the certificate is a small file issued by a trusted Certificate Authority and installed on the server. During the connection, the browser checks that file: who issued it, to whom, whether it has expired, whether it has been revoked. If everything checks out, you get the padlock and an https:// address. If not, a warning.

The key word here is “trusted.” Browsers keep a list of certificate authorities they trust by default. A certificate from such an authority is accepted silently; one you generated for yourself is not, even if the encryption underneath is technically identical. So the whole point of SSL is not only the maths of encryption but also the chain of trust: someone authoritative vouches that the site at this address is genuinely who it claims to be.

HTTP or HTTPS: one letter everyone sees

The difference between http:// and https:// is literally that trailing “s” for “secure.” But the consequences of that letter are visible to the visitor straight away.

On a secure site there is a neutral padlock next to the address. On an insecure one, Chrome has long shown a grey “Not secure” label, and soon it will show a full-screen warning with a confirmation button. Picture someone clicking your Instagram ad and, instead of the product page, hitting a screen that reads “Attackers might be trying to steal your information.” How many of them press “Continue anyway”?

At Netloria we have more than once watched a business owner blame a drop in leads on “the season” or “the algorithm” for weeks, while the cause sat right there in the address bar — the site served content over HTTP, and half of the visitors turned around at the very first screen.

Why HTTPS is no longer optional

A decade ago, encryption was considered necessary only for banks and online stores. Now it is the standard for the entire web, and the numbers confirm it. According to Google, the share of pages loaded over HTTPS in Chrome grew from roughly 30–45% in 2015 to around 95–99% by 2020 — and has held at that level since. Counting public sites only, Windows is at about 98%, and Android and Mac are above 99% (Google Security Blog).

So a site without HTTPS today is that rare exception the browser deliberately draws attention to. And three separate reasons to switch are at work here, not one.

Visitor trust. The padlock and a clean address are things people have learned to notice, mostly without thinking. A “Not secure” label on a checkout page kills conversion more effectively than any typo in your copy.

Search rankings. Google has officially used HTTPS as a ranking signal since 2014. On its own it is a light one — moving to HTTPS will not rocket you to the top. But all else being equal, a secure site has an edge over an insecure competitor, and that is exactly the position most small businesses find themselves in on the results page.

Technical capabilities. Many modern browser features — geolocation, push notifications, service workers for offline mode, correct behaviour of payment forms — simply refuse to work over an unencrypted connection. Without HTTPS you are cutting off part of your toolkit before you have even thought of using it.

Types of SSL certificate: DV, OV and EV

When it comes to choosing, it turns out that “SSL certificate” is not one product but three levels of validation. They differ not in the strength of encryption — that is the same — but in what exactly the authority checks before issuing.

TypeWhat is verifiedIssuing speedWho it suits
DV (Domain Validation)Only that you control the domainMinutes, automaticBlogs, landing pages, most small-business sites
OV (Organization Validation)Domain plus the real existence of the companyHours to a few daysCorporate sites where legal transparency matters
EV (Extended Validation)In-depth organisation check under a strict procedureSeveral days, with documentsBanks, large stores, fintech

Here is a detail that sellers of expensive certificates stay quiet about: EV once showed a green bar with the company name in the address, and that was precisely how it was sold. Modern browsers have removed that green bar. To a visitor, DV, OV and EV now look identical — the same padlock. So paying extra for EV only makes sense where there are real regulatory or internal requirements, not for a “trust effect” the user no longer sees.

How much SSL costs — and why it is often zero

Another question where businesses lose money for no reason. SSL is often sold as a separate paid service for a few hundred a year — even though in the vast majority of cases it is already free.

The non-profit authority Let’s Encrypt issues DV certificates for free, automatically, to anyone. They are valid for 90 days and renew themselves, with no human involved. A huge share of the modern web runs on Let’s Encrypt.

In practice this means the following.

  • Decent hosting attaches a free certificate in its panel with a single toggle — and you never think about it again for years. On how not to pick the wrong provider, we wrote in how to choose web hosting.
  • A paid certificate is genuinely needed only for specific jobs — OV/EV for large organisations, a wildcard for dozens of subdomains, warranties from the authority. For a typical services site or store it is a needless line of expense.
  • If someone charges you “for SSL” on an ordinary site, that is a reason to ask what exactly for, not to pay quietly.

As a web studio based in Ukraine, Netloria sets up a free certificate with automatic renewal by default on every project — so the client never has to think about this technical detail and never gets a surprise a year later in the form of an expired term.

How to tell when something is wrong with your certificate

Having a certificate does not mean everything works. Here are the most common problems that make the padlock disappear or start scaring visitors with warnings. Run through this list on your own site right now.

  • It expired. The most common and most annoying cause. The certificate was there, but renewal was forgotten — and one day the whole site greets visitors with a red screen. Automatic renewal removes this risk entirely.
  • Mixed content. The page itself loads over HTTPS, but images, scripts or fonts on it are still referenced via http://. The browser treats such a page as not fully secure and drops the padlock. A classic trap after migrating an old site to HTTPS.
  • The certificate does not cover every version of the address. It is issued for example.com, but the visitor arrives at www.example.com — and sees an error, because to the browser these are different addresses.
  • A self-signed certificate. Encryption is technically present, but it was issued by the server itself, not a trusted authority. The browser does not trust it and shows a full-screen warning. Sometimes people “save money” this way, not realising the effect is worse than no certificate at all.
  • HTTP does not redirect to HTTPS. The certificate is installed, but the old insecure version of the site still opens in parallel. A search engine sees two copies; a visitor can land on either.

Mixed content is the sneakiest of these, because the site looks almost healthy. Here is a typical scenario from our practice: a business migrates an old site to HTTPS, the home page gets its padlock, everyone relaxes — and a week later they happen to notice the product pages have no padlock, because dozens of images uploaded years ago still carry http:// addresses. Each of those references has to be hunted down in the database and rewritten — sometimes it is hardcoded in the theme, sometimes in the post text, sometimes in a third-party plugin that inserts the full path. That is why we never consider an HTTPS migration finished until we have walked every internal page, not just the home page.

A trivial thing? Not to the browser. The padlock is either honest across the whole page, or it is not there at all.

A basic check takes half a minute: open the site, click the padlock next to the address, look at the expiry date and who the certificate was issued to. If there is no padlock or it is crossed out, deal with it today rather than after Chrome’s October update. And click through a few internal pages too, not only the home page — that is where mixed content hides.

What to do next

The order of action depends on the state your site is in.

If there is no HTTPS at all, start with the hosting: in most panels a free certificate switches on with one click, after which you need to redirect all HTTP traffic to HTTPS and check the site for mixed content. If the certificate is there but the padlock is unstable, the problem is almost always one of the checklist items above, and it is fixed point by point.

A separate situation is when the browser warning appears suddenly after the site has worked fine for a long time. That can be more than an expired certificate — it can be a sign of a hack or tampered settings. What to do in that case we covered in detail in website hacked: what to do. And one adjacent point: the certificate is tied to the domain, so there are pitfalls when choosing that too — more on them in how to choose a domain name.

SSL is one of those cases where the correct setup costs nothing and half an hour of work, while a mistake can quietly drain leads for weeks. It stings to lose customers over a technical detail you did not even suspect existed.

Let’s make your site secure and fast

If you would rather not wrestle with certificate types, redirects and mixed content — that is fine, that is what we are for. Netloria builds corporate websites with correctly configured HTTPS, automatic certificate renewal and a check against every trap listed above — so you can think about customers, not the padlock in the browser. Write to us and we will look at the state your site is in right now.

Frequently asked questions

How do I install an SSL certificate on my website?

On most hosts, a free Let’s Encrypt certificate is enabled with a single toggle in the control panel. After that, set up a permanent redirect from HTTP to HTTPS for all traffic, and on WordPress change the site address in settings to https://. Finally, go through your inner pages and check them for mixed content.

How long is an SSL certificate valid?

Free Let’s Encrypt certificates are valid for 90 days and renew automatically if your host has that set up. Paid certificates are issued for longer but still limited periods and have to be reissued on time. What matters most is automatic renewal, so your site never greets visitors with a warning one morning.

What is the difference between SSL and TLS?

TLS is the modern successor to the SSL protocol, and old SSL versions were switched off long ago because of vulnerabilities. Every certificate sold or issued as “SSL” today actually works with TLS. For a site owner there is no practical difference: it is the same thing under two names.

Why does my browser say “Not secure” even though I have a certificate?

The most common cause is mixed content: the page loads over HTTPS, but images or scripts on it are still linked via http://. Other causes are an expired certificate, one that doesn’t cover the www version, or a site that doesn’t redirect HTTP to HTTPS. Click the icon next to the address to check the expiry date and domain, then open a few inner pages.

Do I need an SSL certificate if my site doesn’t take payments?

Yes. Any form that collects a name and phone number sends personal data, and Chrome warns visitors about every site without HTTPS, payments or not. HTTPS is also a Google ranking signal, and some browser features, such as push notifications and geolocation, don’t work without it.

Обговорюємо саме цю послугу у вашому проєкті?

Corporate Website