Insights:SSL Certificates & HTTPS: 6 Key Concepts You Need to Understand
1. Certificate Types: DV / OV / EV
- DV (Domain Validation): Verifies only domain control; fast issuance; suitable for general websites.
- OV (Organization Validation): Verifies business identity; suitable for B2B / export-oriented sites.
- EV (Extended Validation): Stricter identity verification; browser visual indicators have been largely de-emphasized by major browsers — no need to blindly chase it.
Choose based on your business trust requirements, not simply “the pricier the better.”
2. CA: Who Issues
A CA (Certificate Authority) is a certificate-issuing entity trusted by browsers.
Key points:
- Pick mainstream, widely-trusted CAs.
- Consider CA compatibility and ecosystem support.
- Free certificates are available, but have shorter validity periods and require automated renewal.
- Avoid certificates from unverified sources.
3. Why Browsers Don't Trust the Certificate Chain
The certificate must form a complete chain: Server Certificate → Intermediate Certificate → Root Certificate.
Common Issues:
- Only the server certificate is installed, without the intermediate certificate.
- Certificate chain order is incorrect.
- Root certificate has expired.
- Server and CDN each have only half of the certificate chain.
Verify using an online certificate chain checker or openssl.
4. Domain Coverage: Single Domain, Multi-Domain, Wildcard
- Single domain:
www.example.com. - Multi-domain / SAN: One certificate covers multiple domains.
- Wildcard:
*.example.com, covering only one level of subdomains.
Note:
- Check whether both
example.comandwww.example.comare covered. - When there are many subdomains, a wildcard certificate is more convenient.
- Multiple brands/domains: use SAN or issue certificates separately.
5. Validity Period and Renewal
- Certificates have a clear expiry date.
- Auto-renew before expiration.
- Reload the service after renewal.
- Set up monitoring for expiry alerts.
- Keep rollback certificates on hand.
Certificate expiration is a common cause of "entire site down" incidents.
6. TLS Configuration and HTTPS Details
- Enable TLS 1.2/1.3; disable legacy protocols.
- Configure strong cipher suites.
- Redirect all HTTP traffic via 301 to HTTPS.
- Enable HSTS (after confirming full-site HTTPS).
- Handle mixed content (images/scripts still served over HTTP).
- Add
Secureflag to cookies.
Pre-Launch Checklist
- Certificate domain matches requested domains.
- Certificate chain is complete.
- Validity period is sufficient.
- All HTTP requests redirect to HTTPS.
- No mixed content present.
- TLS version and cipher suites comply with standards.
- Renewal is automated.
- Expiry monitoring is in place.
Common Misconceptions
| Misconception | Consequence |
|---|---|
| Installing only the leaf certificate without the intermediate chain | Some browsers won't trust it |
| Covering only www subdomain | 裸域 errors |
| Not redirecting HTTP | Site remains accessible in plaintext |
| Neglecting mixed content | Lock icon warning |
| Not monitoring expiry | Sudden outage |
Boundaries
HTTPS protects data in transit but does not verify that website content is authentic, nor does it prevent server intrusions. It is the most basic security layer—not a complete solution.
Related reading: