SSL/TLS certificates

Secure your site with an HTTPS address and build your customers’ trust by protecting their data exchanges.

Reviewer 1 Reviewer 2 Reviewer 3 Reviewer 4 Reviewer 5

Join our 4653 satisfied customers

Which certificate level should you choose?

Alpha SSL

Fast and economical, it is ideal for blogs and small showcase sites.

SSL Domain

Validated online, it secures your website with classic HTTPS protection.

Organization SSL

The identity of your organization is verified for increased trust from your customers (OV).

Business SSL

The highest level of certificate security with extensive validation of your identity (EV).

Reviewer 1 Reviewer 2 Reviewer 3 Reviewer 4 Reviewer 5

Join our 4653 satisfied customers

Why install an SSL/TLS certificate?

A secure and verified channel

The SSL certificate (now technically replaced by TLS) acts as the digital passport of a website.

 

Here are the three pillars that explain why it is the cornerstone of online trust:

GlobalSign: Recognized certification authority

Navigators are suspicious by nature… Choosing the certificate from a recognized certification authority (CA) is like having an official passport rather than a hand-drawn identity card: both say who you are, but only one allows you to go through customs without any hassle.

Encrypting mechanisms

The certificate ensures that data are not spied on or modified during transit. Thanks to complex hashing mechanisms, if a hacker tried to intercept and alter a message or transaction between your browser and the server, the connection would be immediately invalidated. This is the guarantee that what you send arrives intact at its destination.

Our certificates


Alpha SSL

Domain SSL

Organization SSL

Business SSL

Version disponibles

Standard & Wildcard*

Standard, Wildcard* & SAN** (UC)

Standard, Wildcard* & SAN** (UC)

Standard & SAN** (UC)

Durée

200 jours

200 jours

200 jours

200 jours

Délai d'obtention

~2 heures

~2 heures

2 à 3 jours ouvrés

3 à 5 jours ouvrés

Prix (sans option)

35 € HT/an

79 € HT/an

179 € HT/an

399 € HT/an

Prix Wilcard

149 € HT/an

290 € HT/an

469 € HT/an

-

Prix SAN complet

(domaine différent)

-

-

80 € HT/an

160 € HT/an

Prix SAN sous domaine

(domaine identique)

-

40 € HT/an

40 € HT/an

80 € HT/an

Nombre de SAN autorisés

-

249

249

249

option UC, SAN gratuits inclus

-

3 gratuits (www/owa/autodiscover/mail)

3 gratuits (www/owa/autodiscover/mail)

Garantie

1 000$

10 000$

1 250 000$

1 500 000$

Pourquoi choisir Namebay ?

Service clients expert

Contrairement aux plateformes automatisées, Namebay place l'humain et l'expertise au centre. Vous bénéficiez d'un accompagnement par des spécialistes. Que ce soit pour une configuration complexe ou une urgence, notre équipe vous apporte une solution concrète et rapide.

Gestion sécurisée

En tant que bureau d'enregistrement accrédité (ICANN), Namebay garantit une sécurité maximale pour vos noms de domaine. Nous offrons des outils de protection avancés (Registry Lock, renouvellement automatique, certificats SSL de haute sécurité) pour assurer la continuité de votre activité et protéger votre identité contre toute tentative de détournement/

25 ans à votre service

Choisir Namebay, c'est opter pour la proximité et la fiabilité d'un acteur historique du Web. Avec plus de 25 ans d'expérience, nous maîtrisons parfaitement les enjeux juridiques et techniques du marché. Notre stabilité et notre connaissance approfondie des extensions (TLDs) mondiales font de nous le partenaire idéal pour le développement de votre stratégie digitale à l'international.5

Plateforme intuitive

L'autonomie de nos clients est une priorité. Notre interface de gestion est conçue pour être à la fois puissante pour les experts et accessible pour les débutants. De plus, nous mettons à votre disposition une base de connaissances en ligne pour vous guider pas à pas dans vos configurations, de l'achat du domaine à l'installation de votre certificat SSL.

Reviewer 1 Reviewer 2 Reviewer 3 Reviewer 4 Reviewer 5

Rejoignez nos XXX clients satisfaits

Vous voulez aller plus loin ?

Nous vous accompagnerons de la meilleure qualité de service possible. Et nous le faisons bien.

FAQ

Consult our frequently asked questions and find the information you need

Do you need to consult our specific documentation for your services?

Can’t find the answer to your question?

How does a TLS SSL certificate work?

To understand how an SSL certificate works, it is useful to picture the full sequence of a secure connection between a browser and a server. When a user enters the URL of a website using HTTPS, the browser first initiates a TLS handshake: it contacts the server and asks it to prove its identity.

The server then sends its SSL certificate, which contains its public key, domain name, the certificate authority that signed it, as well as information about its validity period and cryptographic properties. The browser verifies this certificate by checking the chain of trust up to a root certificate authority already recognised in its certificate store. If the signature is valid, the domain name matches the website being visited, and the certificate is neither expired nor revoked, the browser accepts it.

A shared session secret is then established securely between the browser and the server. From this shared secret, both parties derive symmetric session keys that are used to encrypt all subsequent application data exchanged between them.

The certificate itself is no longer directly involved in encrypting the data; it has fulfilled its initial role: authenticating the server and enabling the creation of an encrypted communication channel. This provides organisations with confidential communications and data integrity, while also giving users a visible signal of trust in their browser.

The ssl certificate protects exchanges between the site and its visitors by encrypting the data transmitted. Its installation is usually done in a few clicks via the host’s dashboard. A protected site not only benefits from a climate of trust but also an advantage in terms of referencing on search engines.

  • Form numbering and online purchases
  • Data theft prevention
  • Google positioning support

In practice, installing an SSL certificate almost always follows the same technical process: first, the administrator retrieves the certificate issued by the certificate authority, the associated private key and, where applicable, the intermediate certificates; the server configuration is then adjusted so that the website responds over HTTPS without any chain-of-trust errors.

On Apache, this step generally involves enabling the SSL module, configuring port 443, and specifying the paths to the crt, key and chain files in the relevant virtual host, before restarting the service and checking the HTTP-to-HTTPS redirection.

On Nginx, the principle is similar, but the configuration is handled within the server block using the dedicated certificate and key directives, while ensuring compatibility with current TLS versions and the use of modern cryptographic algorithms.

For WordPress or other Namebay hosting solutions, each hosting plan includes the installation of a default SSL certificate.

In all cases, the final validation should include checking the padlock, the certificate’s validity period and the absence of mixed-content errors. A poorly deployed certificate provides less protection than it suggests, whereas a rigorous deployment turns a technical requirement into a lasting foundation for trust and performance.

Certification Authorities (CAs) no longer issue certificates that are valid for a full year in a single issuance. The maximum validity period is now set at 200 days.

However, for your convenience, when you purchase your certificate, the offer is still provided for a full 1-year period. Here is how it works in practice:

  1. You purchase your certificate for 1 year.
  2. You receive a first certificate (valid for 200 days).
  3. Before it expires, a second certificate is sent to you automatically to cover the remainder of the year.
Key point: These two certificates are technically identical. They use the same private key and the same parameters. Only the expiration date changes.