SSL Certificates in Kenya: Free vs Paid, Explained

A padlock, the metaphor every SSL certificate is sold with

A client forwarded me an invoice last year with one line that made me put my tea down. “SSL Certificate — Ksh 6,500 per year.”

He was on a plan that already included SSL, for free, renewed automatically. He had paid that invoice for three years.

The certificate was real. The charge was not necessary.

So this is the post I wish somebody had sent him. What free SSL actually is, what paid SSL adds, and the questions that tell the two apart before money changes hands.

There is one rule in it: every figure below is on a page you can open yourself. I am not going to quote a price for a certificate we do not sell, because a number without a provider and a domain count is a guess wearing a suit.

A padlock, the metaphor every SSL certificate is sold with
Photo: Nino Barbieri, CC BY-SA 2.5, via Wikimedia Commons

Free vs paid SSL certificates in Kenya: the three questions that settle it

Most comparisons list certificate types like a menu. That is not how the decision works.

There are only three questions, and the answers decide everything.

Question one: who validates, and how much

A domain-validated (DV) certificate proves one thing: whoever requested it controls the domain. That is all. It takes minutes and it is what free certificates are.

An organisation-validated (OV) certificate also checks that the business exists, with documents. An extended-validation (EV) certificate checks further, and used to turn the address bar green.

For a Kenyan SME selling to local customers, the padlock is the same in all three cases. The difference is paperwork.

Question two: how many names it covers

A single certificate covers one name, usually yourbusiness.co.ke, and often www as a second name.

A wildcard covers every subdomain: shop., mail., blog., all of them. A multi-domain certificate lists several different names, which is useful when you run more than one site.

This is the question that actually changes price. Coverage, not brand.

Question three: who renews it

Free certificates typically last 90 days and renew automatically when the software is set up properly. Paid certificates are usually sold for a year.

If nobody is watching the renewal, both fail. The free one fails more often, in smaller pieces.

The comparison, without the marketing

Free (DV) Paid (DV) Paid (OV/EV)
Padlock in the browser Yes Yes Yes
Validates the domain Yes Yes Yes
Validates the business No No Yes
Wildcard available Often Yes Yes
Renewal Automatic, every 90 days Manual or automatic Manual
Typical buyer Most Kenyan SMEs Many subdomains, or a host without automation Tenders, procurement, regulated buyers
Cost Ksh 0 Per certificate, per year Per certificate, per year, more

Most businesses reading this belong in the first column. The rest of the post is about knowing when you do not.

What buyers actually ask

In practice, nobody asks me about validation levels. Two questions come up instead, and they are better questions.

The first is “is the free one real?” It is, and the next section explains why. The second is “why is this invoice charging me for something my plan has?” That one is usually a sales process, not a technical problem.

If you can answer those two, most SSL certificates in Kenya stop being mysterious. The rest is detail for the people who need wildcards or procurement paperwork.

A cutaway padlock, which is roughly how much most buyers know about what is inside a certificate
Photo: Flickr user 25797459@N06, CC BY 2.0, via Wikimedia Commons

What the padlock actually proves, and what it does not

SSL certificates in Kenya get sold with a lot of language about safety, and most of it is imprecise.

What it does

A certificate does two jobs. It encrypts the connection between the visitor’s browser and your server, so somebody on the same wifi cannot read the card number in transit.

And it proves the visitor reached the domain they typed, rather than something pretending to be it.

That is it. Two jobs, both worth having.

What it does not do

It does not stop your site being hacked. It does not stop malware. It does not make your WordPress plugins safe or your passwords strong.

Plenty of phishing sites have valid certificates, because a certificate only proves control of a domain. A criminal can own a domain.

If a sales page tells you a certificate makes a site “hack-proof”, that page is selling a feeling.

It also does not encrypt the data sitting on your server, which is where most of the damage in a breach actually happens. A certificate protects the road, not the warehouse.

Encryption is not a badge

When a visitor loads your site over HTTPS, the browser and the server agree a key before any content moves. Everything after that agreement is scrambled in transit.

That protects the card number on a shared wifi network, which is worth real money. It protects nothing once the data reaches your server.

So think of SSL certificates in Kenya as a name tag plus an envelope. The name tag says who you are, the envelope hides the contents. Neither stops somebody robbing the shop.

Why Google mentions it

HTTPS is a lightweight ranking signal, as Google’s own guide to HTTPS explains. It is not a magic lift, and it will not outrank better content.

It matters more at the moment of conversion. A browser warning sits between your customer and the payment button, and people close the tab.

The Kenyan checkout test

Open your own site on a phone, on mobile data, and go through the checkout as a customer would. Watch the address bar.

If the padlock is missing at any point, you have found a leak that costs money every day. Fixing it is usually free.

Do the same test on a competitor’s site while you are there. You will notice how quickly you judge a business by that one detail, and that is exactly what your customers do to you.

Why free SSL is not a downgrade

The cheapest certificate on the market is not a weak version of the expensive one. It is a different validation level at the same encryption strength.

What Let’s Encrypt changed

Let’s Encrypt made domain-validated certificates free, automatic and widely trusted. It issues 90-day certificates and expects software to renew them without a human.

Browsers trust those certificates the same way they trust a paid one, because the validation is the same: control of the domain.

That is why the padlock looks identical. It is identical.

What our plans include

Our shared hosting plans list a free SSL certificate on every tier: Ksh 2,000, 3,500 and 4,000 a year. Cloud plans list unlimited SSL certificates, from Ksh 449 a month, and the WordPress plans state free SSL in their FAQ, from Ksh 899 a year.

There is no separate SSL line on those invoices. That is the whole point.

What “unlimited certificates” means in practice

If you host several sites or subdomains, unlimited certificates means you do not pay per name. That is useful for a business running a shop, a blog and a booking page under one domain.

For a single brochure site, one certificate is all you will ever need.

Why hosts give it away

The certificate costs the host almost nothing when the issuing is automated, and it prevents the support ticket that would otherwise arrive every three months.

That is the commercial logic. A valid certificate on every site means fewer warnings, fewer angry calls, and a hosting brand that is not associated with a red browser page.

It is also why paying separately for SSL certificates in Kenya is often unnecessary. The plan already has the incentive to keep it renewed.

Ask your host plainly whether the certificate costs extra. A one-line answer tells you a lot about how the rest of the invoice will read.

What happens behind the scenes

When a plan includes SSL, the host issues the certificate, installs it on the server, and renews it before expiry. Good hosts also monitor expiry and raise it before a customer notices.

Ask which of those three the host does, and where the certificate is installed. On a panel like cPanel the answer is usually visible in one click.

If the panel shows an expiry date, diarise it. Even automated renewal deserves one annual glance.

Network switches and patch panels, where certificates are installed rather than bought
Photo: public domain, via Wikimedia Commons

When free SSL breaks in practice

Free is not the same as automatic-and-forget. Here is what actually goes wrong, in the order I see it.

Expiry nobody noticed

A 90-day certificate renewed by software is invisible. A 90-day certificate renewed by nobody is a warning page every three months, and it always happens on a weekend.

Ask who owns the renewal. If the answer is “the system”, ask what happens when the system breaks.

The domain moved

Changing nameservers, moving to a new host, or switching www to non-www can leave the certificate pointing at a name it does not cover.

The site still loads. The warning still appears.

Mixed content

This is the one everybody misses. The page is HTTPS, but an image, a font or a script still loads over HTTP. The browser calls the page “not fully secure”, and sometimes blocks the element entirely.

A single old image URL in a footer can do it. So can a plugin that was written before HTTPS was normal.

Redirect loops

Forcing HTTPS is a good idea done badly surprisingly often. A redirect that sends HTTPS back to HTTP, and HTTP forward to HTTPS, produces a browser error that looks like the site is down.

The fix is one rule in the configuration, and the diagnosis is ten minutes with a browser.

How to check a certificate in ten seconds

Click the padlock, then the certificate details. You will see who issued it, which names it covers, and when it expires.

Do that on your own site once a quarter. It is faster than waiting for a customer to tell you.

The warning page, from the customer’s side

A browser warning is not a subtle thing. It fills the screen, hides the content, and asks the visitor to click “advanced” before proceeding.

Most people do not click advanced. They close the tab, and you never hear about it, because a customer who bounces does not file a complaint.

That silence is why SSL certificates in Kenya deserve a calendar reminder rather than a one-off setup. The failure is invisible from your side and expensive on theirs.

What to tell your host

Send one message: the URL, a screenshot of the warning if you have it, and the words “the certificate is not valid on this name”.

That is enough for support to find it. A vague “the site is not secure” usually costs an extra round of questions.

A business owner checking her own site the way a customer would
Photo: Bill Branson, public domain, via Wikimedia Commons

When paying for a certificate makes sense

I am not going to pretend paid certificates are always a waste. There are real cases.

You need a wildcard and your setup cannot automate it

Wildcards are convenient when you run many subdomains. Some free options support them, some hosting setups do not automate them well.

If your host cannot issue and renew a wildcard automatically, a paid wildcard for a year is a reasonable purchase.

A buyer requires organisation validation

Tenders, procurement departments and some regulated customers ask for OV or EV. Not because it is more secure, but because their checklist says so.

If a contract depends on it, buy it. That is a business requirement, not a technical one.

You want a named support line

A paid certificate usually comes with a provider who will help install it, and a warranty behind it. For a business with no technical staff, that support can be the actual product.

Ask what the support covers before you pay for it.

The warranty is not insurance for your losses

Certificate warranties are widely misunderstood. They are not a promise to cover your lost sales.

Treat the warranty as marketing, and treat the support as the thing you are buying.

Ask one question to test it: “if the certificate fails to install on my server, what do you do?” A support line answers that in a sentence.

When it is simply an upsell

If your plan already includes SSL, and the certificate on your site is valid and renewing, nobody needs to sell you another one.

That is the invoice at the top of this post. It was not fraud. It was a line item nobody questioned.

The tender case, in practice

Kenyan procurement teams sometimes ask for a certificate with organisation validation, and the request is usually inherited from a template rather than written for the purchase.

You can ask whether domain validation would satisfy them. Sometimes the answer is yes, and the requirement disappears.

When it does not, buy the OV certificate, keep the validation documents, and diarise the renewal. The paperwork is the product, and it is worth having if a contract depends on it.

What a wildcard actually saves

If you run five subdomains and pay per certificate, a wildcard replaces five purchases with one. If your host already covers unlimited names, it replaces nothing.

Count the names before you buy the coverage. Most businesses think they have more subdomains than they do.

Signing a quote, which is what an SSL invoice should be compared against
Photo: Blogtrepreneur, CC BY 2.0, via Wikimedia Commons

How to compare SSL quotes without being overcharged

If you do decide to buy, compare like for like. Certificates are easy to quote badly.

Five questions for any quote

  1. Which names does it cover? One domain, one plus www, a wildcard, or several names.
  2. For how long? One year, two years, three. Multi-year is normal and should be cheaper per year.
  3. What is the renewal price? The first year is often discounted. The renewal is the real number.
  4. Who installs it? Certificate, installation and configuration are three different things.
  5. Who owns it if you move hosts? Ask whether it can be reissued elsewhere, and at what cost.

A quote that cannot answer all five is not a quote. It is a starting position.

Why this post has no paid price

Because we do not sell certificates separately. Our plans include SSL, so there is no separate price list to quote, and inventing one would be worse than saying so.

If that changes, the price belongs on this page with the rest of the numbers.

The comparison that matters

Take the yearly total of your hosting plan, including SSL, and compare it with the yearly total of the alternative, including SSL and installation.

That is the only comparison a business needs. Certificate brand is a detail inside it.

Skip the trust badge

Some resellers bundle a “site seal” and tell you it raises conversions. The seal is an image.

It does nothing your visitors can verify, and it adds a request to every page load. Ask for it if you like the look, but do not pay a renewal for it.

The padlock in the address bar is the signal that matters, and it is already there.

If you want the plan numbers in one place, what hosting costs in Kenya has them, and the nine checks before you pay cover the rest of the buying decision.

Get the answer in writing

The reason SSL invoices survive for years is that nobody keeps the reply. Ask by email, and keep the reply next to the invoice.

A useful reply names the issuer, the names it covers, the expiry date and the renewal price. If any of those is missing, ask again.

That habit is worth more than any comparison table when you are buying SSL certificates in Kenya from a reseller rather than a host.

Getting HTTPS working on your site today

If you are starting from nothing, the order matters. Done in the wrong order, you get loops and warnings.

The order of operations

  1. Register the domain in the business name, if that is not done yet. Our guide to

registering a .co.ke domain covers the paperwork.

  1. Point the domain at the host, and wait until it resolves. Certificates are issued for names

that already work.

  1. Issue the certificate from the hosting panel, or let the host do it automatically on setup.
  2. Force HTTPS with a single redirect rule, once the certificate is live.
  3. Fix mixed content — every image, font and script on HTTP.
  4. Check every page type: home, a product, a blog post, the contact form.
  5. Update old links in emails, invoices and social profiles to https://.

Most of that is an afternoon. The certificate itself is minutes.

On a Host Kenya plan

Shared and cloud plans include SSL, so the certificate is part of setup rather than a separate purchase. On shared hosting it is listed on every tier, and on cloud hosting the plans list unlimited certificates.

If the padlock is missing after setup, that is a support question, not a purchase. Send the URL.

Bring the domain to the same account if you can. A domain on one provider and hosting on another is workable, but every certificate renewal then depends on two logins that both have to work.

What to do after it works

Put the expiry check in a calendar, even though renewal is automatic. Automatic systems fail quietly, and the calendar costs nothing.

Then test the checkout on a phone one more time. HTTPS is only useful if the customer sees it.

Keep a screenshot of the working padlock with the date in the filename. When somebody tells you the site is insecure six months later, that screenshot ends the argument quickly.

If you are moving hosts

Do the certificate as part of the move, not after it. Issue the new certificate before the DNS switch, so the site never serves an unmatched name.

If you are using a WordPress hosting plan, check the certificate on the staging copy too. A staging site on a temporary domain often breaks the padlock in ways the live site does not.

The order matters more than the brand. A free certificate installed in the right order beats a paid one installed in the wrong one.

Frequently asked questions

Are free SSL certificates in Kenya as good as paid ones?

For the padlock and the encryption, yes. Both are domain-validated at the same strength, and browsers treat them the same. Paid certificates add validation paperwork, wildcard coverage and support, not stronger encryption.

Do I need to buy an SSL certificate for my Host Kenya plan?

No. Our shared, cloud and WordPress plans include SSL, and there is no separate SSL charge on those invoices. If someone quotes you for a certificate while your plan includes one, ask what it adds.

How long does a free certificate last?

Let’s Encrypt certificates are valid for 90 days and are designed to renew automatically. That short life is deliberate: it limits the damage when a key is compromised.

Will HTTPS improve my Google rankings?

Slightly. Google describes HTTPS as a lightweight ranking signal, not a major one. It matters far more for customer trust and for avoiding browser warnings at checkout.

What happens if my certificate expires?

Visitors see a full-page browser warning before they reach your site, and most leave. Search engines may also flag the page. Renewal is usually free and quick, but the lost sales are not recoverable.

Can I use one certificate for several domains?

Yes, in two ways. A wildcard covers every subdomain of one domain, and a multi-domain certificate lists several names. Free options support both on many setups, but coverage depends on how your host issues certificates, so ask before you assume.

The short answer

If you run one site on a plan that includes SSL, you need nothing else. Check the padlock once a quarter, fix mixed content when you add something new, and ignore the invoice that offers to sell you a certificate you already have.

That is the short version of SSL certificates in Kenya: free covers almost everyone, paid covers a specific set of requirements, and neither one protects a site from being hacked.

If you run many subdomains, need organisation validation for a tender, or want a named support line, a paid certificate is a fair purchase. Buy it on coverage and renewal price, not on the badge.

Three places to go from here:

  1. See the shared plans — SSL included on every tier, from Ksh 2,000 a year.
  2. Check the cloud plans — unlimited certificates, from Ksh 449 a month.
  3. Ask us to check your certificate — send the URL and we will tell you what the

browser sees.

Support runs 8am to 6pm, Monday to Saturday.