Course contentsShow
← Computer Science
Lesson 2450 of 2,87255. Web SecurityFree lesson

Certificate Validation and Common Errors

Understand how browsers validate certificates and what causes common errors like expired or self-signed certificates.

Certificate Validation and Common Errors

You'll learn how browsers verify digital certificates and why you sometimes see scary security warnings.

When you visit an HTTPS website, your browser doesn't just blindly trust the certificate the server presents—it performs rigorous validation checks. Understanding this process helps you diagnose why secure connections sometimes fail.

How Browsers Validate Certificates

Your browser follows a multi-step verification process:

  1. Chain of Trust Verification: The browser traces the certificate chain back to a trusted root Certificate Authority (CA) stored in its certificate store, exactly as we learned with the certificate chain of trust.

  2. Expiration Check: Certificates have validity periods (not-before and not-after dates). The browser ensures the current date falls within this window.

  3. Revocation Status: The browser may check if the certificate has been revoked before expiration (using mechanisms like CRL or OCSP).

  4. Domain Match: The certificate's Common Name (CN) or Subject Alternative Name (SAN) must match the domain you're visiting. This prevents an attacker from using a valid certificate for a different site.

  5. Signature Verification: Each signature in the chain is cryptographically verified using the issuer's public key.

Common Certificate Errors

Expired Certificate: The certificate's validity period has passed. Like an expired driver's license, it's no longer trusted.

Self-Signed Certificate: The certificate wasn't issued by a recognized CA—the server signed it itself. While the cryptography works, there's no independent verification of identity.

Name Mismatch: Visiting https://example.com but the certificate is for example.org. This could indicate an attack or misconfiguration.

Untrusted Root: The certificate chain doesn't lead back to any CA your browser recognizes.

Key Takeaway: Browsers validate certificates by checking expiration, signature validity, domain match, and chain-of-trust to a known CA; common errors arise from expired certificates, self-signed certificates, or name mismatches—all indicating the server's identity cannot be reliably verified.