SSL/TLS

SSL/TLS Certificates: Types, Configuration and Common Errors

Complete guide to SSL/TLS certificates: what they are, how to configure them correctly, secure TLS versions and how to fix the most common errors.

2026-08-03·Reading time: 9 min

An SSL/TLS certificate is a digital file that authenticates a website's identity and encrypts communication between the server and the user's browser. The acronyms SSL (Secure Sockets Layer) and TLS (Transport Layer Security) refer to the security protocols that manage this encryption. TLS is the modern version; SSL is obsolete although its name remains popular. When a site uses HTTPS, it is using TLS to protect data transmission.

Why is SSL/TLS mandatory?

Without a valid certificate, modern browsers display a 'Not Secure' warning that discourages most visitors. Additionally, Google has penalized sites without HTTPS in search rankings since 2014. From a legal standpoint, transmitting user data without encryption (contact forms, private areas, online stores) may violate GDPR, with fines of up to 4% of annual global turnover.

Types of SSL/TLS Certificates

  • Domain Validation (DV): the most common and fastest to obtain. Only verifies that the applicant controls the domain. Free with Let's Encrypt. Suitable for blogs, informational sites and personal projects.
  • Organization Validation (OV): also verifies that the organization legally exists. Requires documentation. Recommended for corporate websites.
  • Extended Validation (EV): highest level of verification. Suitable for online banking and high-volume e-commerce where user trust is critical.

TLS Versions: What to Use and What to Avoid

  • TLS 1.0 and 1.1: obsolete with known vulnerabilities (BEAST, POODLE). Chrome and Firefox have disabled them. Any server still supporting them is considered insecure.
  • TLS 1.2: today's minimum recommended version. Secure if configured with modern cipher suites (no RC4, no 3DES).
  • TLS 1.3: the most modern and secure version. Faster handshake, eliminates weak algorithms and provides Perfect Forward Secrecy by default. Always enable when possible.

Let's Encrypt: Free Certificates with Automatic Renewal

Let's Encrypt is a non-profit certificate authority issuing free DV certificates valid for 90 days. The Certbot tool automates obtaining and renewing them without manual intervention.

bash
# Install Certbot on Ubuntu/Debian
sudo apt install certbot python3-certbot-nginx

# Obtain and configure certificate for Nginx
sudo certbot --nginx -d yourdomain.com -d www.yourdomain.com

# Verify automatic renewal works
sudo certbot renew --dry-run

Correctly Configuring TLS in Nginx

nginx
server {
    listen 443 ssl;
    server_name yourdomain.com www.yourdomain.com;

    ssl_certificate     /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;

    # Only TLS 1.2 and 1.3
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers HIGH:!aNULL:!MD5:!RC4:!3DES;
    ssl_prefer_server_ciphers on;

    # Session cache for performance
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 10m;
}

Common SSL Errors and How to Fix Them

  • Expired certificate: the most common error. Renew with `sudo certbot renew` or investigate why the automatic systemd timer failed.
  • Self-signed certificate: browsers mark it as insecure. Obtain a certificate from a trusted CA (Let's Encrypt, Cloudflare, DigiCert).
  • Incomplete certificate chain: the server does not send intermediate certificates. Use fullchain.pem instead of cert.pem in Certbot.
  • Domain name mismatch: certificate covers 'yourdomain.com' but user accesses 'www.yourdomain.com'. Get a SAN or wildcard certificate (*.yourdomain.com).
  • TLS 1.0/1.1 enabled: in Nginx add ssl_protocols TLSv1.2 TLSv1.3; to the server block.

DomainScored automatically analyzes your SSL/TLS certificate: validity, expiry date, active TLS versions, cipher suites and certificate chain. Enter your domain to get the full diagnosis with fix instructions.

Check whether your domain has these issues with DomainScored.

Analyze my domain
We use necessary cookies to keep you signed in and protect you against CSRF attacks. If you accept, we will also load Google advertising, which sets its own cookies. If you decline, the site works exactly the same.