SSL certificates.Secure your website.

Choose the names you need to cover first, then the identity checks you need. These are two separate decisions.

• One website: choose single-domain coverage and check whether both the main domain and www are included.
• Several subdomains: choose a wildcard for names such as shop.example.com and mail.example.com.
• Different domains: choose a multi-domain certificate and check the number of names included.

Use the group tabs above, then narrow the results by coverage, validation level and brand. Compare SSL certificates.

Our current entry offer is AskSSL™ Starter: Kshs 750.00 — Billed yearly. The price shown on each certificate card is the full charge for its selected billing term.

• Coverage: a wildcard or multi-domain product has different pricing from a single-domain certificate.
• Validation and brand: compare the certificate type your project needs.
• Additional names: a multi-domain base price covers its included allowance; extra names may cost more.

Choose an available billing term on the card to update the price and order link together.

Not necessarily. Our web hosting plans include free automated SSL. If it covers your site and renews correctly, it may already meet your HTTPS needs.

A separate certificate can be useful when you need:

• Organisation or extended validation for a business requirement.
• A particular certificate brand or product.
• A coverage arrangement that your existing hosting SSL does not provide.

Check your current certificate and hosting settings before buying another. Explore our web hosting plans or ask us which option fits.

SSL is the familiar product name; modern HTTPS connections use TLS. You will often see the terms used together as SSL/TLS.

• The certificate identifies the server for the domain names it covers.
• TLS encrypts data travelling between a visitor’s browser and your server.
• HTTPS is the secure connection your website uses once TLS is configured.

A certificate protects the connection. It does not remove malware, fix vulnerable plugins or replace website backups.

No. A wildcard covers subdomains at one level of a particular domain. For example, *.example.com can cover:

• shop.example.com
• mail.example.com
• support.example.com

It does not cover example.net or a deeper name such as app.shop.example.com. Check that example.com itself is also included in the certificate’s names.

If you need several different domains as well as wildcard coverage, compare the multi-domain wildcard products.

These are validation levels: they describe what the issuing authority checks before issuing a certificate.

• DV — Domain Validation: verifies control of the requested domain.
• OV — Organisation Validation: also checks the organisation’s identity and details.
• EV — Extended Validation: applies more extensive organisation-verification requirements.

They are not three grades of encryption. Choose OV or EV when your project requires verified organisation information, and allow time for the additional checks.

No certificate should be chosen on a promise of a green address bar. Browser interfaces have changed, and the indicators vary between browsers and devices.

OV and EV certificates carry verified organisation information in the certificate details. That is separate from how the browser chooses to display connection information.

Choose your certificate for its coverage and validation requirements. After installation, check that the site opens over HTTPS without certificate errors.

Prepare the covered names and access needed for validation before you order.

1. List the exact names: include the main domain, www and any required subdomains or additional domains.
2. Generate a CSR if required: create the certificate signing request on the server or control panel that will use the certificate. Keep the matching private key secure.
3. Complete domain validation: follow the supported method provided for your order, such as a DNS record or a website verification file.
4. Supply organisation details: OV and EV products require additional checks and may require supporting documents.

Once issued, install the certificate and intermediate chain on your server. Contact us if you need help with your setup.

Issuance depends on successful validation, not just payment. Domain-validated certificates can be issued quickly once the checks pass; OV and EV involve additional organisation checks.

To avoid preventable delays:

• Use the exact domain names required in your order and CSR.
• Make the requested validation file or DNS record accessible.
• Provide complete organisation details and respond to verification requests.
• Check the order status for a failed or pending validation step.

We do not promise a fixed issuance time for every order. Issuance and installation are separate steps.

No. Your paid subscription term and the expiry date of an issued certificate are different. Public TLS certificates have shorter validity periods, so reissuance may be needed during your paid term.

• Billing term: the period you pay for when ordering the product.
• Certificate validity: the dates during which an individual issued certificate can be used.
• Reissuance and installation: obtaining and installing a replacement before the current certificate expires.

Monitor the installed certificate’s expiry date. Do not assume paying a renewal invoice installs a replacement certificate automatically. Read Sectigo’s current validity guidance.

Yes, provided your hosting service supports installing a compatible custom certificate. You do not have to move your domain registration simply to use a certificate.

Before ordering, confirm:

• Your host allows custom SSL certificates on your plan.
• You or the host can generate the CSR and retain the matching private key.
• The required certificate format and intermediate-chain installation steps.
• Who will install replacement certificates when reissuance is due.

Some managed platforms control SSL themselves. Check with that platform before buying a separate certificate.

Start with the exact warning: certificate errors and mixed-content issues need different fixes.

1. Check the hostname: the certificate must cover the address being visited, including www or the required subdomain.
2. Check validity: make sure the installed certificate is current and the device clock is correct.
3. Check the chain: install the required intermediate certificates with the server certificate.
4. Check page assets: replace old HTTP links to images, scripts or stylesheets with HTTPS versions where supported.
5. Check redirects: test the main domain, www, forms and any separate application hostnames.

Send our team the affected URL and exact warning so we can help identify the next step.