That padlock icon in your browser's address bar represents one of the most important security technologies on the internet: SSL/TLS certificates. Understanding how SSL certificates work — explained simply — helps website owners secure their sites and everyday internet users verify whether a website is safe.
What Is SSL/TLS?
SSL (Secure Sockets Layer) and TLS (Transport Layer Security) are cryptographic protocols that encrypt communication between your browser and a web server.
Technical note: SSL is actually the older protocol (last version: SSL 3.0 from 1996). Modern encryption uses TLS (current version: TLS 1.3). However, everyone still says "SSL" colloquially. When someone says "SSL certificate," they mean a certificate used with TLS encryption.
What SSL/TLS Does
- Encrypts data in transit: Prevents anyone between you and the server from reading the data
- Authenticates the server: Proves you're talking to the real website, not an impersonator
- Ensures data integrity: Detects if data was tampered with during transmission
What SSL/TLS Does NOT Do
- Does not guarantee the site is legitimate: A phishing site can have a valid SSL certificate
- Does not protect data on the server: Only data in transit is encrypted
- Does not scan for malware: SSL doesn't check if downloads are safe
- Does not mean the site is trustworthy: It means the connection is encrypted
How SSL Certificates Work
The Handshake (Simplified)
- Client hello: Your browser says "I want to connect securely" and lists supported encryption methods
- Server hello: The server responds with its SSL certificate and chosen encryption method
- Certificate verification: Your browser checks the certificate against trusted Certificate Authorities (CAs)
- Key exchange: Browser and server create a shared encryption key
- Encrypted connection: All further communication is encrypted
This happens in milliseconds before any web page content loads.
Certificate Chain of Trust
SSL certificates are issued by Certificate Authorities (CAs) — trusted organizations that verify the identity of certificate requesters.
Root CA (Built into your browser/OS)
└── Intermediate CA (Issued by Root CA)
└── Your SSL Certificate (Issued by Intermediate CA)
Your browser trusts a set of root CAs. Those root CAs sign intermediate CA certificates, which in turn sign website certificates. This chain creates a verifiable path of trust.
Types of SSL Certificates
By Validation Level
Domain Validated (DV)
- Verifies you own the domain (usually via email or DNS record)
- Issued in minutes
- Cheapest option (free with Let's Encrypt)
- Shows padlock only
- Best for: Personal websites, blogs, small businesses
Organization Validated (OV)
- Verifies domain ownership AND organization identity
- Issued in 1-3 days
- Shows organization name in certificate details
- Best for: Business websites, e-commerce
Extended Validation (EV)
- Most rigorous verification process
- Verifies legal entity, physical address, and operational status
- Issued in 1-5 days
- Previously showed green address bar (most browsers stopped this)
- Best for: Financial institutions, large enterprises
By Coverage
Single Domain: Covers one domain (example.com)
Wildcard: Covers one domain and all subdomains (*.example.com)
Multi-Domain (SAN): Covers multiple specified domains (example.com, example.org, app.example.com)
How to Check SSL Certificate Status
Method 1: Browser Check
Chrome/Edge:
- Click the padlock icon in the address bar
- Click "Connection is secure"
- Click "Certificate is valid" to see full details
Firefox:
- Click the padlock icon
- Click the arrow next to "Connection secure"
- Click "More Information" → "View Certificate"
Safari:
- Click the padlock icon in the address bar
- Click "Show Certificate"
Method 2: Online SSL Checker
Use an SSL checker tool to quickly view:
- Certificate validity dates
- Issuing Certificate Authority
- Certificate chain completeness
- Protocol versions supported
- Cipher suites enabled
You can also verify a site's DNS configuration is correct with a DNS Lookup tool, and check whether the server is responding properly using an HTTP Headers analyzer.
What to Check
| Check | What It Means | Red Flag |
|---|---|---|
| Expiration date | When the certificate expires | Expired = insecure |
| Issuer | Who issued the certificate | Unknown or self-signed CA |
| Domain match | Certificate matches the domain you're visiting | Mismatch = possible phishing |
| Chain completeness | All intermediate certificates present | Incomplete chain = errors on some devices |
| Protocol version | TLS version in use | TLS 1.0 or 1.1 = outdated |
| Key size | Encryption key length | Less than 2048-bit RSA = weak |
Common SSL Errors and What They Mean
"Your connection is not private" (NET::ERR_CERT_DATE_INVALID)
Cause: Certificate has expired.
If you're the site owner: Renew immediately. Enable auto-renewal to prevent recurrence.
If you're a visitor: Don't proceed unless you absolutely trust the site. An expired certificate means encryption may still work, but the site owner isn't maintaining security.
"Certificate authority error" (NET::ERR_CERT_AUTHORITY_INVALID)
Cause: The certificate was issued by an untrusted CA, or it's self-signed.
If you're the site owner: Use a recognized CA (Let's Encrypt is free). Ensure the full certificate chain is installed.
"Name mismatch" (SSL_ERROR_BAD_CERT_DOMAIN)
Cause: The certificate was issued for a different domain than you're visiting.
If you're a visitor: This is a strong warning sign. The site may be impersonating another site.
If you're the site owner: Ensure your certificate covers all domains and subdomains you use, including www and non-www variants.
"Mixed content" warnings
Cause: The page loads over HTTPS, but some resources (images, scripts, stylesheets) load over HTTP.
Fix: Update all resource URLs to use HTTPS or protocol-relative URLs.
Getting an SSL Certificate
Free Options
Let's Encrypt: The most popular free CA
- Automated issuance and renewal
- DV certificates only
- 90-day validity (auto-renewal recommended)
- Supported by most hosting providers
Cloudflare: Free SSL through their CDN
- Shared certificate
- Easy setup—just change nameservers
- Includes additional security features
AWS Certificate Manager: Free for AWS-hosted services
Paid Options
When to pay for SSL:
- OV or EV validation needed for business credibility
- Warranty: Paid certificates typically include a warranty ($10K-$1.75M)
- Support: Dedicated technical support for installation issues
- Wildcard certificates: Cover unlimited subdomains
Popular paid CAs: DigiCert, Sectigo (formerly Comodo), GlobalSign, GeoTrust.
SSL Best Practices for Website Owners
Configuration
- Use TLS 1.2 or 1.3: Disable TLS 1.0 and 1.1 (deprecated)
- Enable HSTS: HTTP Strict Transport Security forces HTTPS connections
- Redirect HTTP to HTTPS: Ensure all HTTP requests redirect to HTTPS
- Use strong cipher suites: Disable weak ciphers (RC4, 3DES)
- Enable OCSP Stapling: Faster certificate validation for visitors
Maintenance
- Set up auto-renewal: Never let certificates expire
- Monitor expiration dates: Use alerts as backup to auto-renewal
- Test regularly: Use SSL checker tools to verify configuration — also run a URL Status check to confirm your site responds correctly over HTTPS
- Update when vulnerabilities are found: Stay informed about SSL/TLS vulnerabilities
- Verify port accessibility: Ensure port 443 (HTTPS) is open and reachable with a Port Checker
Common Configuration Mistakes
- Incomplete certificate chain: Install intermediate certificates, not just the end-entity cert
- Mixed content: One HTTP resource breaks the padlock
- Forgetting subdomains: Ensure certificates cover all subdomains in use
- Not redirecting HTTP: Both HTTP and HTTPS versions accessible confuses visitors and search engines
SSL and SEO
Google confirmed HTTPS as a ranking signal in 2014, and it's become a baseline expectation:
- HTTPS is a minor ranking factor: Won't dramatically boost rankings, but lack of HTTPS can hurt
- Chrome warnings drive visitors away: "Not Secure" warnings increase bounce rate
- HTTP/2 requires HTTPS: Faster page loads from HTTP/2 are only available over HTTPS
- Referral data: HTTPS preserves referrer information in analytics
Conclusion
SSL/TLS certificates are the foundation of web security. For website owners:
- Get a certificate — Let's Encrypt is free and takes minutes
- Configure properly — Use TLS 1.2+, redirect HTTP to HTTPS, fix mixed content
- Maintain it — Auto-renew and monitor regularly
- Test it — Use checker tools to verify your setup
For internet users, the padlock icon means the connection is encrypted, but it doesn't guarantee the site is trustworthy. Always verify you're on the correct domain, especially for banking, shopping, and entering sensitive information.
Want to check a website's SSL certificate? Try our SSL Checker — instantly view certificate details, expiration dates, and security configuration for any domain.
Related Reading
- DNS Lookup Guide — understand how domain names resolve to IP addresses, a critical step before SSL even begins
- Client-Side Security: Why Processing Data in Your Browser Matters — learn why browser-based tools are safer for checking sensitive configurations
- Password Security in 2026: Best Practices — complement your SSL knowledge with strong credential management