Skip to main content

HTTPS and Certificate Options

SSL Certificates

Use TLS to encrypt data in transit between a visitor and your website. Compare certificate validation and domain coverage, then request current pricing for your requirements.

A network cable connection beside a small metal padlock

SSL certificate options

DV SSL

Domain control validation

Custom quote

Certificate scope

  • Validation of domain control
  • HTTPS for the names listed in the certificate

OV SSL

Organisation identity validation

Custom quote

Certificate scope

  • Domain and organisation validation
  • Document checks by the certificate authority

EV SSL

Extended organisation validation

Custom quote

Certificate scope

  • Extended organisation validation
  • Identity checks by the certificate authority

Certificate selection and HTTPS

Choose SSL by domain coverage and validation requirements

An SSL certificate is used with TLS to authenticate the hostnames it covers and encrypt data in transit. Selecting one involves two separate decisions: which names need coverage and what identity validation is required. Map your website, subdomains and application endpoints first, then compare the certificate options with the environment where HTTPS will terminate.

A website on one domain

List the exact names visitors use, including whether both the base domain and its www address are needed. Check those names against the selected certificate's coverage. Plan redirects to your preferred HTTPS address and update internal links so that pages do not continue loading images, scripts or forms through HTTP.

Several services under one domain

A wildcard can cover names at one subdomain level, such as shop.example.com and app.example.com. It does not automatically cover deeper names such as api.app.example.com. Check base-domain coverage separately and consider how the private key will be protected if the certificate is installed on several services.

An organisation with identity requirements

OV and EV certificates include organisation checks by the certificate authority. Consider them when your business or procurement process requires that verification. Prepare the requested organisation details and authorised contacts. Validation type does not itself provide stronger encryption, and it should not be treated as a guarantee about a website's content or seller.

Selection guide

Validation and coverage answer different questions

Choose the validation process and hostname coverage together. DV, OV and EV describe checks made by the issuer; wildcard describes a coverage pattern. Review the exact product and issuance requirements when requesting an offer.

Scroll horizontally to see the full table →

OptionWhat it establishesWhat to check
Domain validation · DVControl of the requested domainAvailable domain verification method and included hostnames.
Organisation validation · OVDomain control and organisation informationRequired documents, contact verification and the intended coverage.
Extended validation · EVExtended organisation checks under the issuer's processEligibility, validation requirements and your organisation's need.
Wildcard coverageCoverage for one subdomain level under the stated nameBase-domain inclusion, subdomain depth and private-key handling.
Several unrelated namesA requirement to cover different hostnamesAsk which certificate option supports the complete name list.

Your next step

Treat installation and renewal as one process

Issuing a certificate is only one part of enabling HTTPS. Record where certificates are installed and who will renew them, including any proxy, load balancer or CDN in front of the application.

  • Prepare the request in the right environment

    Confirm the required hostnames and create the certificate request using the appropriate server or panel workflow. Protect the private key and keep it out of ordinary email or support messages. Use the agreed secure process if installation assistance is needed.

  • Complete the issuer's validation

    Arrange access to DNS, the required HTTP path or the approved email method, depending on the product. For organisation validation, ensure the requested details are accurate and the responsible contact is available. Issuance timing depends on completing these checks.

  • Test the complete HTTPS path

    Install the certificate and required chain, check hostname matches and review redirects. Test application logins, forms and embedded content. Mixed-content warnings or incorrect redirects require application configuration work even when the certificate itself is valid.

  • Track expiry and renewal ownership

    Keep a list of covered names, installation points and expiry dates. Confirm the selected product's current renewal conditions and whether validation must be repeated. After replacement, verify the certificate actually served to visitors rather than relying only on a successful order.

Operating HTTPS

Install your SSL certificate and keep HTTPS working

An SSL/TLS certificate is used when establishing an encrypted connection between a visitor’s browser and a server. Selecting domain coverage, installing the certificate chain and tracking renewal are parts of the same process.

Certificate validation, connection encryption and overall website security involve different checks. Use these steps to verify the connection and how your website uses HTTPS after installation.

  1. Verify names
  2. Test HTTPS
  3. Track renewal

Check the names the browser validates

During the TLS handshake, the browser checks the hostname, certificate validity and trust chain. The server must present the right certificate and prove possession of its associated private key.

Compare coverage with your base domain, www address and other required subdomains. Do not assume wildcard coverage: list each required name and confirm whether the certificate includes it before ordering.

Verify during installation

  • Required hostnames and the certificate chain presented
  • Validity dates and the correct server configuration

Maintain application security alongside encryption

After a successful TLS handshake, application data sent over that connection is encrypted. This protection alone does not prevent unauthorised access to the server or a user account.

Manage updates, account permissions and application security separately. A browser’s HTTPS indicator describes the connection; it does not guarantee that a seller is trustworthy or that the content contains no malicious software.

Manage together

  • Updated applications, appropriate access and secure accounts
  • Private-key protection and independent data backups

Use one preferred HTTPS address consistently

Choose the primary address you want visitors and search engines to use. Redirect HTTP and other domain versions to the appropriate HTTPS address, avoiding unnecessary redirect chains.

Update internal links, canonical URLs and the sitemap to match. Check images, scripts and form destinations for remaining HTTP addresses. A paid certificate alone does not deliver an increase in search rankings.

Test on your website

  • Redirects, canonical URLs and sitemap addresses
  • Forms, images and mixed-content warnings

Verify the replacement after renewal

Certificate expiry and a service billing period are different things. Track renewal requirements and domain validation, and keep the required DNS or server access available.

After installing a replacement, test the names, dates and chain seen by an external connection. If you use multiple servers or a load balancer, check every relevant connection endpoint.

Track for continuity

  • Certificate expiry and required renewal validation
  • Deployment of the replacement to all relevant servers

Share the domain names to protect and your server or control panel so we can review certificate coverage and installation requirements.

Discuss certificate coverage

Choosing and renewing an SSL certificate


What does an SSL/TLS certificate protect?

TLS encrypts data in transit between a browser and the server. It does not replace application security updates, account protection or backups.


How do DV, OV and EV differ?

DV validates control of a domain. OV and EV add checks of the organisation behind it. The validation level concerns identity checks; it does not by itself make the connection encryption stronger.


Which domain names will the certificate cover?

List the exact hostnames you need before ordering. A wildcard such as *.example.com covers one level, such as shop.example.com, but not api.shop.example.com. The base domain must also be included in the certificate.


How are price and issuance time determined?

The issuer, validation type and covered names determine the offer. Issuance also depends on completing domain or organisation validation. Contact us with the required names for the current price and scope.


When should I renew?

Check the expiry date of the issued certificate and the renewal requirements of the issuer. A billing period and a certificate validity period are different. Plan renewal before expiry and verify the replacement on the server.


Will a paid certificate improve my Google ranking?

HTTPS supports a secure browsing experience. Buying a paid certificate or choosing EV does not guarantee higher rankings. Content, accessibility and the rest of the website still matter.


How can I prepare for installation?

Identify the server or control panel and the names to protect. Generate the required key and certificate request in the appropriate environment, install the issued chain and check HTTPS and renewal. Keep private keys private.

Let’s move your project forward

The right service. A team you can reach.

Choose the right channel for package selection, migration planning or a question about an existing service.

+90 850 307 0123