SSL Certificate

Protocols & Standards
Secure Sockets Layer certificate.
← Back to Glossary

What is an SSL Certificate?

An SSL certificate (Secure Sockets Layer certificate) is a digital certificate that authenticates a website's identity and establishes an encrypted connection between a web server and browser. Although SSL has been superseded by TLS (Transport Layer Security), the term "SSL certificate" remains widely used. These certificates are essential for HTTPS websites, displaying the padlock icon that signals security to visitors.

How SSL Certificates Work

The Handshake Process

1. Browser requests secure connection

2. Server sends SSL certificate + public key

3. Browser verifies certificate with CA

4. Browser creates session key, encrypts with public key

5. Server decrypts with private key

6. Encrypted session established

Certificate Types

By Validation Level

TypeValidationTimeTrust LevelUse Case
DV (Domain)Domain ownership onlyMinutesBasicBlogs, small sites
OV (Organization)Business verification1-3 daysMediumBusiness websites
EV (Extended)Extensive verification1-2 weeksHighestBanks, e-commerce

By Coverage

TypeCoversExample
Single domainOne domainexample.com
WildcardDomain + all subdomains*.example.com
Multi-domain (SAN)Multiple specific domainsexample.com, example.org

Certificate Authorities (CAs)

Trusted entities that issue certificates:

Obtaining an SSL Certificate

Free Options (Let's Encrypt)

# Using Certbot

sudo certbot --nginx -d example.com -d www.example.com

# Auto-renewal

sudo certbot renew --dry-run

Commercial Purchase Process

1. Generate CSR (Certificate Signing Request)

2. Submit to Certificate Authority

3. Complete validation (DV/OV/EV)

4. Download and install certificate

DNS Configuration (CAA Records)

Specify which CAs can issue certificates:

example.com. CAA 0 issue "letsencrypt.org"

example.com. CAA 0 issuewild "letsencrypt.org"

Certificate Components

ComponentPurpose
Public keyEncrypts data sent to server
Private keyDecrypts data (keep secret!)
Certificate chainLinks to trusted root CA
Validity periodExpiration date (typically 90 days - 1 year)

Best Practices

1. Use TLS 1.2+: Disable older protocols

2. Automate renewal: Prevent expiration outages

3. Secure private key: Never share or expose

4. Use strong ciphers: Configure secure cipher suites

5. Implement HSTS: Force HTTPS connections

6. Monitor expiration: Set up alerts before expiry

Common Issues

SSL certificates are fundamental to web security, enabling encrypted communications that protect sensitive data during transmission.

Put This Knowledge to Work

Use DomScan's API to check domain availability, health, and more.