Check a live domain's certificate, or upload a .pem / .crt / .cer file for deep technical analysis.
An SSL/TLS certificate enables HTTPS — the encrypted connection between a browser and a server. Without it, all data exchanged (including passwords and form submissions) travels as plaintext. Browsers mark HTTP sites as "Not Secure," and Google gives HTTPS sites a ranking advantage. Today, free certificates from Let's Encrypt make there's no excuse not to have one.
Domain Validation (DV) only verifies that you control the domain — fast, free, and sufficient for most sites. Organization Validation (OV) additionally verifies the legal business entity. Extended Validation (EV) is the highest level, requiring extensive identity checks; it used to show the company name in the browser bar but modern browsers have largely removed that distinction.
Common reasons: supporting deprecated TLS versions (1.0/1.1), using weak cipher suites, missing HSTS headers, a certificate chain that doesn't include intermediate certificates, or a certificate close to expiry. Enabling TLS 1.3 only and adding an HSTS header is often enough to move from B to A.
Let's Encrypt provides free, automated DV certificates renewed every 90 days. Most hosting platforms and CDNs (Cloudflare, Netlify, Vercel) provision Let's Encrypt certificates automatically when you point your domain. For self-managed servers, the Certbot tool handles issuance and renewal automatically.
This tool checks the certificate presented to the public — what browsers and users actually see. If your site is behind Cloudflare or another CDN, the certificate you see here is the CDN's certificate, not the origin certificate. The origin-to-CDN connection may use a separate certificate that is not visible from a public SSL check.