Choosing the Right SSL Certificate for an E-Commerce Site in 2026

reading time Reading Time: 34 minutes

Ask most store owners how they chose their SSL certificate and the answer is some mix of price, the padlock, and a half-memory that the expensive ones used to turn the address bar green. That reasoning held up for about a decade. It doesn't anymore.

Three things changed underneath it. Browsers stopped giving any visual reward for higher-validation certificates in 2019. Chrome is now switching to HTTPS-first behaviour for every public website, warning people before it loads a page that isn't encrypted. And since 15 March 2026, no publicly trusted certificate can be valid for longer than 200 days. That ceiling halves again in March 2027 and keeps falling until 2029.

Put those together and choosing an SSL certificate for an e-commerce site stops being a one-off purchase. It becomes an operating decision with four parts: which identity checks you actually need, which hostnames the certificate has to cover, how renewal will happen several times a year without anyone remembering to do it, and how the certificate fits around your checkout and server. This guide works through each decision in order, corrects the myths that still circulate in older buying guides, and shows where Canadian privacy law and hosting location change the answer.

The short answer. For most online stores, the right certificate is a domain-validated (DV) certificate from a publicly trusted certificate authority, covering every hostname the store uses and renewed automatically. Choose organization validation (OV) when a bank, payment partner or business customer needs your verified legal identity inside the certificate. Extended validation (EV) is rarely worth its cost and paperwork now that browsers no longer display it. Whichever you choose, the server's TLS configuration and the renewal process do more for shoppers' safety than the validation level does.

What an SSL certificate actually does for an online store

An SSL certificate is a digitally signed file that binds your domain names to a cryptographic public key. When a shopper's browser connects, your server proves it holds the matching private key, the browser checks that a certificate authority (CA) it trusts signed the certificate, and the two sides agree on encryption keys for that session. The result is a connection that nobody in between can read or alter, to a server the browser has confirmed is authorized to answer for that domain.

Strictly speaking, these are TLS certificates. The original SSL protocols were retired years ago, and every secure connection a modern browser makes uses TLS. The industry still says "SSL" out of habit, and so does this article.

What it protects in a store

In a store, the certificate covers far more than card numbers. Every one of these travels between the shopper's device and your server:

  1. Account logins, password resets and the session cookies that keep a shopper signed in and their cart attached to them.
  2. Names, shipping and billing addresses, phone numbers and email addresses, all of which are personal information under Canadian privacy law.
  3. Order history, wish lists and saved payment references.
  4. Card details, whenever they are typed into a page that your server delivers.
  5. Your own admin logins, which are the keys to the entire store.

What it does not do

A certificate secures the road, not the destination. It does nothing for a server running an unpatched plugin, a database with a weak password, or a checkout page that loads a compromised third-party script. The card-skimming attacks that payment industry rules now specifically target work perfectly well over HTTPS, because the malicious code runs inside the encrypted page. And a certificate says nothing about whether a business is honest. Phishing sites get valid certificates every day, because the most common type checks only that the applicant controls the domain.

A certificate does A certificate does not
Encrypt data between browser and server Protect data stored on your server or in backups
Prove the server is authorized for the domain Prove the business behind the domain is trustworthy
Stop tampering with pages in transit Stop malicious scripts you load yourself
Allow modern, faster protocols such as HTTP/2 Fix vulnerable plugins, themes or server software
Meet a baseline expectation of browsers and payment rules Make a store PCI DSS compliant on its own

Keep that distinction in mind while shopping, because much of what gets sold as "more security" is really more identity paperwork.

Six myths from older SSL buying guides

Many of the articles that rank for this topic were written before the changes above, and some of their advice is now wrong. These six come up most often.

Myth 1: Free certificates use weaker encryption

Encryption strength depends on the TLS version, the cipher suite and the key type your server negotiates with the browser. It does not depend on what you paid for the certificate. A free DV certificate from a publicly trusted CA uses the same key types and signature algorithms as a paid one, and browsers treat the two identically. What paid products can add is a higher validation level, human support, a relying-party warranty and multi-year service terms. Those may be worth paying for, but stronger encryption is not on the list.

Myth 2: You need a dedicated IP address for SSL

This was true when each HTTPS website needed its own IP address, because the server could not tell which certificate to present until the encrypted connection already existed. Server Name Indication (SNI), a TLS extension standardized in RFC 6066 in 2011, fixed that by letting the browser name the site it wants at the very start of the handshake. Every browser a shopper is realistically using today sends SNI. Some hosting platforms still pair certificates with dedicated IPs for their own operational reasons, so ask your host, but HTTPS itself no longer requires one.

Myth 3: EV certificates turn the address bar green

They used to. Apple removed EV indicators from Safari in 2018, and Chrome 77 and Firefox 70 followed in late 2019, moving the organization name out of the address bar and into the page-information panel that appears only when someone clicks. Google's stated reason was that its own research, along with earlier academic work, showed the indicator did not change how people behaved. Chrome later replaced the padlock itself with a neutral settings-style icon. Today a shopper looking at an EV-secured checkout sees exactly what they see on a DV-secured one.

Myth 4: Higher-validation certificates rank better in Google

Google confirmed HTTPS as a lightweight ranking signal in 2014, and its page experience documentation still lists serving pages over HTTPS. Nothing in Google Search Central's documentation treats one validation level differently from another. The search benefit comes from running HTTPS cleanly: one redirect hop, no mixed content, and canonical tags, sitemaps and internal links that all point to the HTTPS version.

Myth 5: The warranty protects your store

Certificate warranties are relying-party warranties. Under conditions the CA sets, they compensate people who lost money because the CA wrongly issued a certificate. They do not cover a breach of your store, chargebacks, downtime or your own misconfiguration. Read the terms if a warranty figure is part of the sales pitch, and never treat it as a substitute for cyber insurance.

Myth 6: A shared certificate is fine for a small shop

"Shared SSL" meant using a certificate issued for your host's server name, so your secure pages lived at an address on the host's domain rather than yours. That can be acceptable for reaching a control panel. It is wrong for a store, because shoppers land on an unfamiliar domain at the moment they are asked to trust you with payment details, and many store platforms expect your own domain on the certificate. A certificate for your own domain now costs little or nothing, so there is no reason to compromise.

Decision 1: Validation level (DV, OV or EV)

Validation level describes how much a certificate authority checks before it issues. A DV certificate confirms that the applicant controls the domain. An OV certificate adds verification that a named legal organization exists and requested the certificate. An EV certificate adds stricter, standardized identity checks defined by the CA/Browser Forum's EV Guidelines.

Domain validation (DV) Organization validation (OV) Extended validation (EV)
What the CA checks Control of the domain (DNS record, file on the web server, or email to a domain contact) DV checks plus legal existence, address and phone, verified against official sources OV checks plus stricter identity, authority and operational checks
Typical time to issue Minutes, and fully automatable Usually one to several business days for first vetting Usually longer than OV
Organization name in the certificate No Yes Yes, with jurisdiction and registration number
Wildcard available Yes Yes No
What shoppers see Standard browser security icon Same as DV unless they open certificate details Same as DV unless they open certificate details
Typical fit Most online stores B2B sellers, partner or procurement requirements A specific contractual or regulatory requirement

When DV is the right call

For most stores, DV is enough. Shoppers decide whether to trust you based on the site itself, its policies, reviews and the payment options they recognize, not on certificate fields they never open. DV issuance can be fully automated, which, as the next sections explain, is now the property that matters most.

When OV earns its place

OV makes sense when someone outside your business needs to confirm, from the certificate itself, which legal entity operates the domain. Common triggers are a bank, payment partner or enterprise customer whose security questionnaire asks for it, and B2B buyers whose procurement teams check vendor certificates. It can also help when your brand is a phishing target, because anyone checking can see the verified legal name behind the real domain.

Plan for the paperwork. Since March 2026, a CA can reuse your organization's verified identity details for no more than 398 days, so OV means re-vetting at least once a year on top of the shorter certificate renewals.

When EV still makes sense

EV now fits a narrow set of cases: a contract, regulator or payment partner that specifically requires it. It costs more, takes longer, cannot be issued as a wildcard, and gives shoppers nothing visible in return. If nobody is requiring it, put the budget into automation, monitoring and server hardening instead.

A paperwork tip for Canadian businesses

OV and EV vetting compares your order details against government business registries, federal or provincial depending on where you are incorporated or registered. The certificate shows the legal name the registry holds. For a numbered company, that might be a string of digits followed by "B.C. Ltd." or "Ontario Inc.", which customers will not recognize. Operating or trade names are often registered separately at the provincial level. Get your registrations, addresses and phone listings consistent before ordering, because mismatches are the most common reason vetting stalls.

Decision 2: Coverage (single-domain, multi-domain or wildcard)

Coverage is about which hostnames one certificate protects. Before choosing a product, list every hostname your store answers on, including the ones that only redirect. A typical small store's list looks something like this:

Hostname Purpose Needs a certificate?
example.ca Main storefront Yes
www.example.ca Storefront or redirect Yes, even if it only redirects
example.com Brand protection redirect Yes, even if it only redirects
account.example.ca Customer accounts Yes
blog.example.ca Content site Yes
staging.example.ca Testing Yes, but keep it separate from production
cdn.example.ca Images and scripts you serve Yes, if you serve it yourself

The redirect rows catch people out. A browser has to complete a secure connection to example.com before it can receive the instruction to go to example.ca, so a redirect-only domain without a valid certificate shows a full-page security warning instead of redirecting.

Single-domain certificates

These cover one hostname. Most CAs include both the bare domain and its www version, but check rather than assume. A single-domain certificate suits a store that runs everything on one hostname.

Multi-domain (SAN) certificates

A multi-domain certificate lists specific hostnames in its Subject Alternative Name field, and they can span different domains: example.ca, example.com and shop-brand.ca on one certificate. It is the tidy choice for a store with a fixed, known set of names.

Every hostname you list becomes public. Publicly trusted certificates are recorded in Certificate Transparency logs, which anyone can search. If a certificate names admin-portal.example.ca or old-staging.example.ca, you have just published those names.

Wildcard certificates

A wildcard certificate for *.example.ca covers any single level of subdomain: shop.example.ca and account.example.ca, but not example.ca itself unless the CA adds it, and not a.b.example.ca. Wildcards hide individual hostnames from Certificate Transparency logs and make adding a new subdomain easy.

The trade-off is key spread. The same private key ends up on every server that uses the wildcard, so a breach of a forgotten staging box exposes the key that also protects your checkout. Automated issuance of wildcards also generally requires DNS-based validation, which means your automation needs permission to edit DNS records.

Store setup Sensible coverage
One storefront, one domain Single-domain certificate covering bare and www
Storefront plus a .com redirect and an accounts subdomain Multi-domain certificate for those exact names
Many subdomains that change often Wildcard for production, with a separate certificate and key for staging
Separate servers for store, blog and staging Separate certificates per server, so one compromise stays contained

Decision 3: Lifetime and renewal, the change most guides miss

In April 2025, the CA/Browser Forum, the body where certificate authorities and browser makers agree the rules for publicly trusted certificates, passed Ballot SC-081v3. It sets a fixed schedule for shrinking how long a certificate can be valid, and how long a CA can rely on an earlier check that you control your domain.

Certificates issued on or after Maximum validity Domain validation reuse
Before 15 March 2026 398 days 398 days
15 March 2026 200 days 200 days
15 March 2027 100 days 100 days
15 March 2029 47 days 10 days

We are in the 200-day phase now. In five months the maximum drops to 100 days. By 2029, a certificate will last about six and a half weeks, and the CA will need fresh proof of domain control almost every time it issues one.

What this means for an online store

"Multi-year" certificates are now subscriptions. You can still buy two or three years of coverage, but the certificate itself is reissued several times within that term. Each reissue has to be generated, installed and served correctly.

Manual renewal stops being realistic. At 100 days, each certificate needs replacing about four times a year. At 47 days, roughly eight. Multiply that by every certificate across your storefront, redirect domains, staging and any separate servers, and a calendar reminder is no longer a renewal process.

An expired certificate takes the store offline. Browsers show a full-page warning that most shoppers will not click past, so sales stop. Payment and shipping services that call back to your server over HTTPS, to confirm a payment or update an order, can fail their own certificate checks, leaving orders stuck in a pending state. And PCI DSS requirement 4.2.1 specifically requires that certificates protecting card data in transit be valid and not expired or revoked.

Automate issuance and renewal

The industry's answer is ACME, the Automated Certificate Management Environment protocol published as RFC 8555 in 2019. An ACME client on your server proves domain control to the CA, requests the certificate, installs it and repeats the process well before expiry, with no human involved. Many hosting control panels run this automatically for DV certificates. Several commercial CAs also support ACME for OV certificates once the organization has been vetted, so choosing OV no longer has to mean manual renewals.

Questions worth putting to your host or developer:

  1. Is certificate issuance and renewal automated for every hostname, including redirect-only domains?
  2. Which validation method does the automation use, and will it still work if DNS moves or a firewall rule changes?
  3. If you use a wildcard, does the automation have API access to your DNS provider?
  4. Who gets alerted when an automated renewal fails, and how far ahead of expiry?

Monitor even when renewal is automated

Automation fails quietly. A DNS change, a new firewall rule, a CAA record that no longer lists your CA, or a server migration can all break renewal without anyone noticing until the certificate expires. Some CAs have also stopped sending expiry reminder emails altogether. External monitoring that checks every hostname daily and alerts at around one third of the certificate's lifetime remaining gives you time to fix a failure before customers see it.

Decision 4: The certificate authority and the key behind it

Use a publicly trusted CA, and stay portable

A storefront certificate must come from a CA included in the major browser and operating system trust stores. Self-signed certificates and private corporate CAs have their uses inside an organization, but never on a public store.

Trust is not permanent. Browser makers have withdrawn trust from certificate authorities several times when they failed to meet compliance obligations, including in 2024 and 2025. When that happens, sites using the affected CA have a deadline to switch. With automated issuance, switching CAs is a configuration change. With a manually installed multi-year certificate, it is a project. Treat portability between CAs as part of the decision.

Publish a CAA record

A Certification Authority Authorization (CAA) record, defined in RFC 8659, is a DNS entry naming the CAs allowed to issue certificates for your domain. Publicly trusted CAs have been required to check it since 2017. It takes minutes to set up and closes off one route to mis-issued certificates. Remember to update it whenever you change CA or add one for a wildcard, or automated renewals will be refused.

Choose the key type deliberately

Most certificates use either an RSA key (2048 bits or longer) or an ECDSA key on the P-256 curve. ECDSA keys are smaller and faster to process during the handshake, which helps busy checkouts and mobile shoppers. RSA has the widest compatibility with very old clients. Many servers can present both and let each visitor's software pick. Whichever you choose, generate the private key on your own server and never send it by email or store it in a shared drive.

Watch Certificate Transparency logs

Since 2018, Chrome has required publicly trusted certificates to appear in Certificate Transparency logs, which are public and searchable. That cuts both ways. It exposes the hostnames in your certificates, but it also lets you spot a certificate issued for your domain that you never requested. Several free services will alert you when a new certificate for your domain appears.

How your checkout design changes the certificate decision

Where the card number is typed determines how much of the payment security burden sits on your own server, which changes what your certificate is protecting. The Payment Card Industry Data Security Standard (PCI DSS) recognizes this through its self-assessment questionnaires (SAQs). Which questionnaire applies to you is confirmed with your payment processor or acquiring bank, but the common patterns look like this:

Checkout model Where the card number is entered Usual questionnaire What your certificate protects
Redirect to a hosted payment page The processor's own page and domain SAQ A, if all eligibility criteria are met Everything before the redirect, the redirect itself, accounts and personal information
Payment fields embedded from the processor (iframe) The processor's frame inside your page SAQ A, if all eligibility criteria are met The page that loads the frame, which an attacker could alter to swap in a fake one
Fields your page creates and posts to the processor Your page, with data sent directly to the processor SAQ A-EP The page that collects the card data
Card data received by your server Your page and server SAQ D The card data itself, in transit to you

In January 2025, the PCI Security Standards Council revised SAQ A. It removed the payment-page script requirements 6.4.3 and 11.6.1 from that questionnaire and added an eligibility criterion instead: the merchant must confirm their site is not susceptible to attacks from scripts that could affect their e-commerce systems. Redirect and embedded-frame stores still have to think about what code runs on their pages. Our guide to first-party data collection and payment-page scripts covers those script controls in more depth.

What PCI DSS 4.0.1 says about certificates

Two requirements bear directly on certificates for any store in scope:

  1. Requirement 4.2.1 requires strong cryptography whenever card numbers travel over open, public networks, and requires that the certificates involved be confirmed as valid and not expired or revoked.
  2. Requirement 4.2.1.1, mandatory since 31 March 2025, requires an inventory of the trusted keys and certificates used to protect card numbers in transit.

An inventory sounds bureaucratic, but with renewals every few months it is the only reliable way to know what you have. For a small store, a spreadsheet works: hostname, certificate type, issuing CA, key type, where the private key lives, expiry date, how renewal happens, and who owns it. Even a store whose questionnaire does not require one benefits from keeping it.

PCI DSS has not permitted the original SSL protocols or early TLS for protecting card data since mid-2018, which is one more reason the server configuration below matters.

This section is general information about PCI DSS, not compliance advice. Confirm your questionnaire type and obligations with your payment processor or a qualified security assessor.

The certificate is half the job: server configuration matters more

Install the same certificate on two servers and you can get two very different levels of protection. The configuration around the certificate decides which protocol versions are allowed, whether browsers can be tricked into falling back to plain HTTP, and whether pages load content insecurely.

Allow only TLS 1.3 and TLS 1.2

TLS 1.0 and 1.1 were formally deprecated by RFC 8996 in 2021, and browsers no longer accept them. The Canadian Centre for Cyber Security's guidance on securely configuring network protocols (ITSP.40.062) sets out acceptable TLS versions and cipher suites and is a sound reference for whoever configures your server. TLS 1.3 also completes its handshake in fewer network round trips, which matters for speed, as the next section explains.

Redirect everything to HTTPS in one hop

Every HTTP request, on every hostname, should receive a single permanent redirect to the HTTPS version of the same page. Chains such as HTTP to www to HTTPS to the final URL waste time and dilute the signals search engines use to pick a canonical address.

Add HSTS, carefully

HTTP Strict Transport Security (HSTS, RFC 6797) is a response header that tells browsers to use HTTPS for your domain for a set period, even if someone types or clicks a plain HTTP link. It stops a class of attacks that strip encryption on public Wi-Fi. Start with a short duration, confirm nothing breaks, then raise it to a year. Add the includeSubDomains setting only after every subdomain works over HTTPS, and treat browser preload lists as a long-term commitment, since removal takes time.

Eliminate mixed content

A page loaded over HTTPS that pulls images, scripts or stylesheets over HTTP is serving mixed content. Modern browsers either upgrade those requests or block them, which can quietly break product images or checkout scripts. After any migration, search the database and theme files for hard-coded http:// addresses and fix them at the source.

Prepare for HTTPS-first browsing

Google announced that Chrome 154, scheduled for October 2026, turns on the "Always Use Secure Connections" setting by default for public sites. Chrome will try HTTPS first and warn people before loading a public page that is only available over HTTP. Old links in email campaigns, printed flyers, QR codes and directory listings will now hit your HTTPS endpoint first, so every hostname, including redirect-only domains, needs to answer on HTTPS with a valid certificate.

Serve the full certificate chain and test from outside

Your server should present your certificate together with the CA's intermediate certificate. Desktop browsers often paper over a missing intermediate, but some mobile apps, payment callbacks and older clients do not, which produces errors that are hard to reproduce. After every certificate or configuration change, test from outside your network with an external TLS checker and from a phone on mobile data.

HTTPS, page speed and search visibility

HTTPS used to carry a reputation for slowing sites down. Today the opposite is closer to the truth, provided the server is set up well.

Why HTTPS can make a store faster

Browsers support HTTP/2 and HTTP/3 only over encrypted connections. Those protocols let a page request many files at once over a single connection, which suits product pages full of images, scripts and stylesheets. A store still on plain HTTP is stuck with the older protocol.

The cost HTTPS does add is the handshake. Before the first byte of a page arrives on a new connection, the browser and server exchange messages to set up encryption, and each exchange is a round trip across the network. A full TLS 1.2 handshake needs two round trips. TLS 1.3 needs one, and returning visitors can resume an earlier session more cheaply still.

Why distance matters

Round trips are bound by distance. Light in optical fibre covers roughly 200 kilometres per millisecond, so the theoretical minimum round trip between Vancouver and Toronto is about 34 milliseconds, and real-world routes add more. A shopper in Mississauga connecting to a server in Vancouver pays that cost for every round trip of every new connection. A checkout that opens fresh connections to your store, your payment processor and your shipping-rate service multiplies it.

This is where e-commerce hosting in Canada becomes a performance decision as well as a privacy one. Serving Canadian shoppers from a nearby Canadian data centre shortens every handshake. 4GoodHosting, for example, operates data centres in Vancouver and Toronto, and the physics above is the reason a Canadian store's hosting location deserves the same attention as its certificate. For how server response time feeds into Google's page experience measures, see our guide to Core Web Vitals and hosting performance.

What search engines actually reward

The search benefit of HTTPS is real but modest, and it comes from a clean setup rather than from certificate type. Make sure canonical tags, XML sitemaps, hreflang annotations and internal links all use HTTPS URLs, that HTTP addresses redirect in one hop, and that Search Console covers the HTTPS property. A broken certificate does far more damage than a cheap one, because crawlers and shoppers both hit the same warning page.

The Canadian angle: privacy law, data location and who sees what

Encryption is an expected safeguard under PIPEDA

The Personal Information Protection and Electronic Documents Act (PIPEDA) requires organizations to protect personal information with security safeguards appropriate to its sensitivity. Its safeguards principle (clause 4.7.3 of Schedule 1) says protection methods should include technological measures, and names encryption as an example. A store that collects names, addresses and order histories over unencrypted connections would struggle to argue it met that standard.

PIPEDA also requires organizations to report breaches of security safeguards to the Office of the Privacy Commissioner, and to notify affected individuals, when a breach creates a real risk of significant harm, and to keep records of every breach. Quebec's private-sector privacy law, as amended by Law 25, adds its own confidentiality incident register and notification duties for businesses that handle Quebecers' personal information.

This is general information, not legal advice. Privacy obligations depend on your province, your customers and how you handle data. Federal privacy reform has also been before Parliament, so confirm current requirements with a lawyer.

Your certificate authority never sees your customers' data

A common worry is whether a Canadian store needs a Canadian certificate authority. It doesn't, for privacy purposes. The certificate contains only public information: your domain names, your public key and, for OV or EV, your registered business details. The private key is generated and kept on your server. The CA is never part of the encrypted conversation between shopper and store, so it never sees a single order, address or card number, wherever it happens to be based.

What decides where customer data lives is everything else: your hosting server, database, backups, and the third-party services you send data to. That is where Canadian hosting matters. Keeping the store and its database in Canadian facilities makes it simpler to tell customers where their information is held. PIPEDA doesn't, on its own, require data to stay in Canada, but it does hold you accountable for information you transfer to service providers. Quebec's law goes further, requiring an assessment before personal information is communicated outside the province.

Judge a host on criteria, not rankings

Store owners often search for the "most secure hosting in Canada", but hosting security doesn't reduce to a single ranking, and a provider's own claim to the title tells you little. A more useful approach is to ask any host the questions that actually determine how safely your certificate and store will run:

  1. Are certificates issued and renewed automatically for every hostname, and who is alerted if renewal fails?
  2. Which TLS versions are enabled by default, and can you control HSTS and redirects?
  3. Which software layers does the host patch, and which are your responsibility? Our guide to website patch management explains how that split works.
  4. Is your store isolated from other customers' sites, through a virtual private server or a dedicated server, or does it share resources on a shared plan?
  5. Where are the servers and backups physically located, and how often are backups tested?

Security on the modern web is a set of overlapping layers, which we cover in why the website itself has become the security perimeter. The certificate is one of those layers, not the whole defence.

Three store scenarios

These are composite examples built from common store setups. They are illustrations, not client case studies.

A one-person ceramics shop in Nova Scotia

The owner sells about forty products, runs everything on one domain, and sends shoppers to a hosted payment page to pay. Card numbers never touch her server.

The right choice is a DV certificate covering the bare domain and www, issued and renewed automatically by her hosting platform. She should add HSTS once she's confirmed every page loads over HTTPS, publish a CAA record, and set up a free external monitor that emails her if the certificate gets within a few weeks of expiry. Paying for OV or EV would buy her nothing her customers would see. The money is better spent on reliable backups and keeping plugins patched.

A growing outdoor gear retailer in Calgary

The store runs on www.example.ca, owns the .com version as a redirect, has customer accounts on a subdomain, a blog on another subdomain, and a staging site the agency uses for testing. Payment fields are embedded from the processor in a frame.

Production gets a multi-domain DV certificate, issued through ACME, that names exactly the storefront, the .com redirect and the accounts subdomain. The blog server, which runs different software, gets its own certificate so a compromise there doesn't expose the storefront's key. Staging sits behind a password, uses a separate certificate, and is never listed on the production certificate. Because the retailer relies on SAQ A eligibility, it also controls which scripts load on the page that hosts the payment frame, and keeps a simple certificate inventory that it reviews monthly.

A B2B distributor in Ontario

This distributor sells supplies to clinics, schools and municipalities, mostly on account terms but with on-site card payments for smaller orders. Several customers send security questionnaires that ask for the legal entity named on the vendor's certificate.

Here OV is justified. The distributor chooses a CA that supports automated OV issuance after the first vetting, puts the annual identity re-vetting on its compliance calendar, and keeps its registry details consistent with the order. Because card data is entered on its own pages, it falls under a broader PCI DSS questionnaire, so the certificate inventory, TLS configuration and expiry monitoring all become evidence it must produce. Running the store on an isolated server rather than shared hosting makes that evidence simpler to gather and defend.

Common mistakes to avoid

  1. Covering www but not the bare domain, or the reverse. Shoppers type both, and one of them will show a warning.
  2. Forgetting redirect-only domains. The .com you bought for brand protection needs a valid certificate to redirect anyone.
  3. Buying multi-year to "set and forget". The term is multi-year, but the certificate isn't. Something still has to reinstall it every few months.
  4. Copying a wildcard key everywhere. One compromised staging server or contractor laptop then exposes production.
  5. Listing private hostnames on a public certificate. Certificate Transparency logs publish them.
  6. Changing CA without updating CAA. Renewal fails quietly until the old certificate expires.
  7. Turning on HSTS preload too early. If a subdomain still needs plain HTTP, you have locked yourself into a problem that takes time to undo.
  8. Leaving out the intermediate certificate. Desktop browsers may cope, but payment callbacks and mobile apps often don't.
  9. Treating the certificate as PCI compliance. It is one control among many, and a skimming script runs happily over HTTPS.

Checklist: choosing an SSL certificate for an e-commerce site

  1. List every hostname the store answers on, including redirects, subdomains and staging.
  2. Decide the validation level by asking who, outside your business, needs to verify your legal identity. If nobody does, choose DV.
  3. Choose coverage (single, multi-domain or wildcard) based on that hostname list and how many servers hold the key.
  4. Confirm issuance and renewal are automated for every certificate, ahead of the 100-day limit that starts on 15 March 2027.
  5. Set up external expiry monitoring with alerts that reach a person who can act.
  6. Publish a CAA record naming the CA, or CAs, you actually use.
  7. Configure TLS 1.3 and 1.2 only, single-hop HTTPS redirects, and HSTS once everything works.
  8. Fix mixed content and serve the full certificate chain.
  9. Record each certificate in an inventory: hostname, CA, key type, expiry, renewal method and owner.
  10. Confirm with your payment processor which PCI DSS questionnaire applies and what it expects of your certificates and pages.

If your store runs on 4GoodHosting, these are fair questions to put to the support team: which certificate your plan includes, which hostnames it covers, how renewal is handled, and what changes if you add a subdomain or move to a VPS. The answers will tell you whether the certificate you already have does the job, or whether one of the options on our SSL certificates page fits your store better.

FAQ

What type of SSL certificate does an e-commerce site need?

Most online stores need a domain-validated (DV) certificate from a publicly trusted certificate authority that covers every hostname the store uses and renews automatically. An organization-validated (OV) certificate is worth it when a bank, payment partner or business customer needs your verified legal identity in the certificate. Extended validation (EV) rarely justifies its cost now that browsers no longer display it.

Is a free SSL certificate safe for an online store?

Yes, provided it comes from a publicly trusted certificate authority and is installed on a properly configured server. Free DV certificates use the same encryption and key types as paid ones, and browsers treat them identically. Paid certificates can add identity validation, support and warranties, but not stronger encryption.

Is an EV certificate worth it for an e-commerce site?

Usually not. Since 2019, the major browsers have shown no visual difference for EV certificates, so shoppers see the same thing on an EV checkout as on a DV one. EV costs more, takes longer to issue and cannot be a wildcard. Choose it only if a contract, regulator or payment partner specifically requires it.

Does the type of SSL certificate affect Google rankings?

No. Google uses HTTPS as a lightweight ranking signal, but nothing in its documentation treats DV, OV and EV differently. Rankings benefit from a clean HTTPS setup: one-hop redirects, no mixed content, and canonical tags, sitemaps and internal links that all use HTTPS.

How often do SSL certificates need to be renewed now?

Certificates issued from 15 March 2026 can be valid for at most 200 days. The limit drops to 100 days on 15 March 2027 and to 47 days on 15 March 2029, under CA/Browser Forum Ballot SC-081v3. That means two renewals a year now, about four from 2027 and about eight from 2029, which is why automated renewal is essential.

Do I need a wildcard certificate for my online store?

Only if you run many subdomains that change often. A wildcard covers one level of subdomain under one domain, but the same private key then sits on every server that uses it. Stores with a fixed set of hostnames are usually better served by a multi-domain certificate, or by separate certificates for separate servers.

Does an SSL certificate make my store PCI compliant?

No. PCI DSS requires strong encryption and valid, unexpired certificates wherever card data travels over public networks, plus an inventory of those certificates. But compliance also covers patching, access control, script management and much more. Your payment processor will tell you which self-assessment questionnaire applies to your checkout.

Does my certificate authority need to be Canadian to meet PIPEDA?

No. The certificate authority never sees your customers' data. It signs a certificate containing only public information, and your private key stays on your server. Where customer data is stored and processed depends on your hosting, database, backups and third-party services. That is where data-location decisions, such as choosing Canadian hosting, actually matter.

What happens if my store's SSL certificate expires?

Browsers show a full-page security warning that most shoppers will not click past, so sales effectively stop. Payment and shipping services that call back to your server over HTTPS may also fail, leaving orders stuck. For stores in PCI DSS scope, an expired certificate protecting card data is also a compliance failure.

Key Takeaways

  1. For most online stores, a DV certificate from a publicly trusted CA, renewed automatically and covering every hostname, is the right choice.
  2. OV is justified when someone outside your business needs your verified legal identity in the certificate. EV is rarely worth it, because browsers stopped displaying it in 2019.
  3. Maximum certificate validity is 200 days now, 100 days from 15 March 2027 and 47 days from 15 March 2029. Automated renewal and expiry monitoring are no longer optional.
  4. Map every hostname before choosing coverage, including redirect-only domains, and keep staging keys separate from production.
  5. Checkout design decides what your certificate protects. PCI DSS 4.0.1 requires valid certificates and an inventory of them wherever card data travels.
  6. Server configuration (TLS 1.3 and 1.2 only, one-hop redirects, HSTS, no mixed content) matters more than validation level.
  7. Your certificate authority never sees customer data. Where that data lives is a hosting decision, which is where Canadian data centres and privacy law come in.

Conclusion

The certificate decision used to be about how much trust a store could buy, signalled by a colour in the address bar. That signal is gone, and what replaced it is less visible and more demanding. A store now needs certificates that cover every hostname it answers on, renew themselves several times a year, sit on a server configured to current standards, and fit the way its checkout handles card data.

Get those right and a modest DV certificate protects shoppers as well as anything on the market. Get them wrong and no validation level will save a checkout that goes dark on a Saturday morning because a renewal failed. The SSL certificate for an e-commerce site is now one part of an operating routine, and the routine is what keeps the store open.

The next deadline is 15 March 2027, when the maximum drops to 100 days. Any store still renewing by hand has until then to change how it works.

Whether you are setting up a new store or tidying up an old one, the questions in this guide are the ones to settle first: which hostnames need cover, who needs to verify your identity, and how renewal will keep happening without you. If you would like a second pair of eyes on your setup, talk to the 4GoodHosting team about your store's hostnames, checkout model and hosting location, or compare SSL certificate options for the validation level and coverage your store actually needs.

Get in Touch

message
Your form has been submitted successfully.
We'll be in touch with you shortly.
Your email address will not be published. Fields marked with an asterisk (*) are mandatory.
+1 S
You may also like: