Skip to main content

Insights

Why SSL Certificates Matter

SSL certificates protect data, build trust and keep browsers from warning visitors away. Learn why they matter and how to stop expiry causing outages.

Published
Updated
Reading time
6 min read
No threats foundMFA enforced

An SSL certificate is a small file installed on your web server that does two important jobs. It allows browsers to encrypt the connection between your visitors and your website, and it proves that the site they are talking to really belongs to your domain. Without it, data travels in plain text and browsers warn visitors that your site is not secure.

Strictly speaking, modern certificates are used with TLS (Transport Layer Security), the successor to the older SSL protocol, which is now obsolete. The name "SSL certificate" has stuck, and we use it here because that is the term most people search for.

For most businesses, the question is no longer whether to use a certificate. HTTPS is the expected baseline. The real questions are whether your certificates are configured correctly, whether they cover everything they need to, and whether renewal is managed reliably enough that an expiry never takes your site, API or email offline.

What an SSL certificate actually does

Encrypts data in transit

When a visitor submits a contact form, logs in or enters payment details, TLS encryption stops anyone between them and your server, such as on public Wi-Fi, from reading or modifying that data. This matters for every page, not just checkout, because session cookies and login credentials travel on ordinary pages too.

Proves identity

A certificate is issued by a certificate authority (CA) that has verified control of the domain. When a browser connects, it checks that the certificate is valid, trusted, unexpired and issued for that exact hostname. This helps protect visitors from being silently redirected to an impostor site.

Protects integrity

Encryption also prevents content being altered in transit. Without HTTPS, networks can inject advertising or malicious scripts into pages your visitors receive.

Why it matters to the business

Browser warnings drive visitors away

Modern browsers label HTTP pages as "Not secure", particularly where forms are involved. An expired or misconfigured certificate is worse: browsers display a full-page warning that most visitors will not click through. For an e-commerce site or lead-generating site, that is effectively an outage.

Customer trust

Visitors may not understand certificates, but they notice warnings. A security warning on your website suggests that the business is careless with data, which is the opposite of the impression you want to create.

Search visibility

Google has used HTTPS as a lightweight ranking signal since 2014. It will not lift a weak page to the top of results, and no provider can guarantee rankings, but serving the site over HTTPS is part of a sound technical foundation. Mixed content and redirect problems can also cause indexing issues. Our SEO health audit checks for these.

Compliance expectations

Frameworks such as PCI DSS require strong cryptography when cardholder data is transmitted over public networks, and data protection regulations such as GDPR expect appropriate technical measures to protect personal data. Encryption in transit is one of those measures. SupportSafe supports the technical controls, but does not provide legal or compliance certification advice.

Modern web features depend on it

Many browser features, including service workers, geolocation and HTTP/2 as implemented by major browsers, require a secure context. Without HTTPS, parts of a modern website or application simply will not work.

Types of certificate

TypeWhat is validatedTypical use
Domain Validated (DV)Control of the domainMost websites, blogs, stores and applications
Organisation Validated (OV)Domain plus the organisation's identityBusinesses wanting organisation details in the certificate
Extended Validation (EV)Stricter organisation checksSome financial and enterprise sites; browsers no longer show a distinct EV indicator in the address bar
WildcardCovers all first-level subdomains of a domainEstates with many subdomains
Multi-domain (SAN)Lists several specific hostnamesSeveral related domains on one certificate

For most business websites, a correctly configured DV certificate, often free from Let's Encrypt or included with hosting, provides the same encryption strength as a paid certificate. Paid certificates may make sense for OV or EV validation, warranty terms or specific organisational requirements.

Why certificates cause outages

Certificates fail in predictable ways, which means most certificate outages are preventable.

Expiry

Every certificate has an expiry date. Let's Encrypt certificates are valid for 90 days, and the industry is moving towards shorter lifetimes: the CA/Browser Forum has agreed a schedule that progressively reduces the maximum validity of publicly trusted certificates over the next few years. Shorter lifetimes improve security but make manual renewal impractical. Automation is no longer optional.

Automated renewal that quietly stops working

Automated renewal is excellent until it fails. Common causes include DNS changes that break domain validation, a firewall or redirect rule blocking the validation request, a server migration that left the renewal job behind, expired API credentials for DNS validation, and a renewed certificate that was never reloaded by the web server. Let's Encrypt also stopped sending expiry reminder emails in 2025, so many site owners lost a safety net they did not know they relied on.

Incomplete coverage

A certificate that covers example.com but not www.example.com, or a main site certificate that misses the shop, API or mail subdomain, will produce errors on the parts that are not covered.

Configuration problems

Missing intermediate certificates, support for outdated TLS versions, weak cipher suites, mixed content where pages load scripts or images over HTTP, and missing HTTP to HTTPS redirects all reduce security or trigger warnings.

Forgotten certificates

Load balancers, CDNs, mail servers, VPN gateways and internal tools often have their own certificates, managed separately from the main website. These are the ones most often forgotten.

Managing certificates properly

A reliable approach to certificates combines automation, visibility and ownership.

  1. Inventory every certificate. List each hostname, where its certificate is installed, who issued it, how it renews and when it expires.
  2. Automate renewal wherever possible. Use ACME-based tools or your hosting platform's built-in automation.
  3. Monitor expiry independently. Use an external check that alerts well before expiry, regardless of whether renewal is automated. This is a standard part of good server monitoring.
  4. Check the configuration, not just the date. Periodically test TLS versions, cipher suites, the certificate chain and security headers such as HTTP Strict Transport Security (HSTS).
  5. Fix mixed content. Make sure every asset loads over HTTPS, and redirect HTTP requests to HTTPS.
  6. Review after changes. DNS changes, migrations and new subdomains are the moments when certificates most often break.

A quick self-check

You can answer most of these questions in an afternoon, and the answers tell you whether your certificate management is under control:

  • Do you know every hostname your business uses, including subdomains for the shop, API, mail and marketing tools?
  • For each one, do you know when its certificate expires and how it renews?
  • Would anyone be alerted if a renewal failed, without relying on the certificate authority to email you?
  • Do all HTTP requests redirect to HTTPS, and do pages load without mixed content warnings?
  • Are outdated protocols such as TLS 1.0 and 1.1 disabled?
  • Is HSTS enabled, and does whoever manages it understand that it commits browsers to HTTPS-only access for the period specified?

If any answer is "not sure", that is the place to start. Fixing the gaps is usually straightforward once they are visible: most of the work is establishing an accurate inventory, confirming that automation runs end to end, and adding an independent expiry alert that reaches a person who will act on it.

Domain registration

Domains deserve the same attention. A lapsed domain registration takes down your website and email together, and it can be much harder to recover than a certificate. Our domain, DNS and SSL management service brings certificates, DNS records and domain renewals into a single monitored inventory.

You can find definitions of terms such as TLS, HSTS and certificate authority in our technical glossary.

The bottom line

SSL certificates are a basic requirement for any business website, but "having one" is not the same as managing them well. The common failures, expiry, broken automation, incomplete coverage and weak configuration, are predictable and preventable with an inventory, automated renewal and independent monitoring.

If you are not sure when each of your certificates expires or whether they are configured correctly, our free website health check includes an SSL and HTTPS review and will flag anything that needs attention.

Frequently asked questions

Is a free SSL certificate as secure as a paid one?
In terms of encryption, yes. A free domain-validated certificate such as one from Let's Encrypt uses the same encryption standards as a paid DV certificate. Paid certificates may offer organisation validation, warranties or support, which some businesses need.
What happens when an SSL certificate expires?
Browsers show a full-page security warning, and many visitors will leave rather than continue. APIs, integrations and payment callbacks that connect to the site may also fail, so an expired certificate can effectively take parts of your business offline.
Do I need SSL if my website does not take payments?
Yes. HTTPS protects logins, form submissions and session cookies, avoids 'Not secure' labels in browsers, and is required for many modern browser features.
What is the difference between SSL and TLS?
TLS is the modern successor to SSL. Older SSL versions are obsolete and insecure, but the term 'SSL certificate' is still widely used for the certificates that TLS relies on.

SupportSafe Engineering Team

Maintenance, infrastructure and security engineers

Articles are written and technically reviewed by the SupportSafe engineers who carry out website, application and server maintenance for our clients. Each article is reviewed for accuracy before publication and updated when practices change.

Let's take responsibility for your technology.

Tell us what you run and what keeps you up at night. We'll assess it and recommend a maintenance plan that fits – with no obligation.