Skip to content

Public Authority Certificates

Understanding Digital Certificates (SSL/TLS)

Section titled “Understanding Digital Certificates (SSL/TLS)”

Digital Certificates, commonly known as SSL/TLS certificates, are small data files that cryptographically link an organization’s (or individual’s) details to a cryptographic key. When installed on a web server, a certificate enables secure connections between the server and a client’s browser, typically using the HTTPS protocol. This protects data in transit by encrypting it.

A digital certificate essentially acts as a digital ID or passport for a website, issued by a trusted third-party organization called a Certificate Authority (CA). The CA verifies the identity of the certificate applicant before issuing the certificate.

When you visit an HTTPS-secured website, your browser checks the site’s SSL certificate. It looks for a padlock icon in the address bar and verifies the certificate’s validity and issuer. This ensures you are connected to the legitimate server and not an imposter, and that your communication is encrypted.

A digital certificate contains several pieces of information, visible in its details:

  • Subject: The name of the entity (domain name, organization) the certificate was issued to.
  • Issuer (Certificate Authority): The name of the CA that verified and issued the certificate.
  • Serial Number: A unique identifier for the certificate, assigned by the CA.
  • Validity Period (Valid-From and Valid-To): The dates defining when the certificate is valid. Certificates expire and must be renewed.
  • Public Key: The public part of the key pair used for encryption. The corresponding private key is kept secret on the server.
  • Signature Algorithm: The algorithm used by the CA to sign the certificate, verifying its authenticity.
  • Digital Signature: The CA’s digital signature, confirming the certificate’s integrity and origin.
  • Key Usage: Specifies the cryptographic purposes for which the public key can be used (e.g., digital signature, key encipherment).
  • Thumbprint (or Fingerprint): A hash of the certificate, used as a shorthand way to identify it.

CAs are trusted entities that issue digital certificates. Browsers and operating systems maintain a list of trusted CAs. If a website presents a certificate issued by a CA in this trusted list, the browser will trust the certificate (provided it’s not expired or revoked and matches the domain).

Examples of CAs include Let’s Encrypt, DigiCert, Sectigo, and GlobalSign.

CAs use different levels of validation before issuing certificates:

This is the most basic level of validation. The CA verifies that the applicant has administrative control over the domain name for which the certificate is requested. Validation is typically done via email confirmation, by adding a DNS record, or by uploading a specific file to the website. DV certificates are quick to issue and are widely used (e.g., Let’s Encrypt provides DV certificates). They provide encryption but offer minimal identity assurance beyond domain control.

Organization Validation (OV) SSL Certificates

Section titled “Organization Validation (OV) SSL Certificates”

In addition to domain control, the CA verifies the legal existence and identity of the organization requesting the certificate. This involves checking business registration documents and other official records. OV certificates provide a higher level of trust as they confirm the legitimacy of the organization. The organization’s name is typically displayed in the certificate details.

This involves the most rigorous validation process. The CA performs a thorough vetting of the organization, including its legal, physical, and operational existence, and confirms that the applicant is authorized to request the certificate on behalf of the organization. While EV certificates used to trigger a prominent green address bar in most browsers, this visual indicator has been largely phased out. However, the verified organization name is still prominently displayed in the certificate details and by clicking the padlock, providing the highest level of assurance about the website owner’s identity.

  • Encryption: Secures data exchanged between the user and the server, protecting sensitive information like passwords, credit card details, and personal data from eavesdropping.
  • Authentication: Verifies that the user is communicating with the legitimate website server and not an imposter site.
  • Trust: The padlock icon and HTTPS prefix signal to users that the site is secure, increasing their confidence and trust.
  • SEO Benefits: Search engines like Google use HTTPS as a positive ranking signal.
  • Compliance: Many regulations and industry standards (e.g., PCI DSS for handling card payments) require the use of SSL/TLS encryption.

In today’s web, SSL/TLS certificates and HTTPS are no longer optional; they are a fundamental requirement for any website.