What Does an SSL Checker Do?
An SSL checker connects to a domain on port 443 and retrieves the certificate the server presents. It then reports key details including expiry date, issuer, subject alternative names (SANs), chain trust, and whether the certificate hostname matches the domain queried.
Certificate Expiry
SSL certificates have a maximum validity period of 398 days (about 13 months). An expired certificate causes browser warnings that drive visitors away and signals to search engines that a site may be abandoned. Many web servers, CI pipelines, and monitoring tools track certificate expiry to trigger renewal before it lapses.
Subject Alternative Names (SANs)
A single certificate can cover many hostnames via its SAN list. For example, a certificate for example.com commonly includes www.example.com and may include subdomains. Wildcard certificates use *.example.com to cover any single subdomain level. This tool lists every SAN so you can verify coverage.
Certificate Chain and Trust
A complete trust chain runs from your domain certificate through one or more intermediate certificates up to a root certificate trusted by the browser. A missing intermediate causes untrusted errors on some clients even if the root CA is trusted. TLS 1.0 and 1.1 were deprecated in RFC 8996; this tool reports the TLS version the server negotiated so you can confirm TLS 1.2 or higher is in use.
Related tools
- Check domain expiry alongside certificate expiry with the WHOIS lookup.
- Confirm HSTS is set in the response headers at HTTP headers.
- Verify CAA records that restrict which CAs can issue certificates with the DNS lookup.
How the SSL Checker Works
The tool opens a TLS connection directly to the domain on port 443 using PHP's OpenSSL stream context. The connection captures the full certificate chain presented by the server: the end-entity certificate, any intermediate certificates, and their relationship to a trusted root. The connection is initiated with SNI (Server Name Indication) so that servers hosting multiple domains on a single IP return the correct certificate for the queried hostname.
No external certificate database is queried; the data comes directly from your server. This means the tool shows exactly what a browser would receive when visiting the domain. If the server presents a self-signed, expired, or hostname-mismatched certificate, that is what the tool reports.
Common Use Cases
- Monitoring expiry before auto-renewal: Let's Encrypt certificates are valid for 90 days. While most hosting panels auto-renew, checking the expiry date directly confirms renewal is working. A certificate expiring in fewer than 30 days with no renewal in progress warrants investigation before the site shows browser security warnings.
- Verifying SAN coverage after adding subdomains: When adding new subdomains (e.g.
api.example.com), the existing certificate must be reissued or a new certificate issued to include the new SAN. Checking the SANs of the certificate served by the new subdomain confirms whether the correct certificate has been deployed. - Confirming the intermediate chain is complete: Some server configurations omit intermediate certificates, relying on browsers to fetch them via AIA (Authority Information Access). Android devices and curl do not follow AIA by default, causing TLS errors on those clients. Checking the certificate chain confirms whether all intermediates are being served.
- Auditing TLS protocol version: TLS 1.0 and TLS 1.1 were deprecated by RFC 8996 in March 2021 and are disabled in all major browsers. PCI DSS 3.2 requires TLS 1.2 as a minimum for payment card data environments. The SSL checker reports the TLS version negotiated, allowing you to confirm TLS 1.2 or higher is in use.
- Pre-deployment certificate validation: Before deploying a new application to a domain, running an SSL check confirms that the certificate is correctly installed and the full chain is present. Certificates installed without the intermediate can pass validation on the deployment server (which caches the chain locally) but fail for external clients.
Standards and Further Reading
TLS 1.3 is specified in RFC 8446. The deprecation of TLS 1.0 and 1.1 is documented in RFC 8996. The CA/Browser Forum publishes the Baseline Requirements that govern certificate issuance, including the 398-day maximum validity period adopted in 2020.
Frequently Asked Questions
What does an SSL certificate checker do?
An SSL certificate checker connects to a domain on port 443 and retrieves the TLS certificate the server presents. It reports the certificate's expiry date, issuer (the Certificate Authority that signed it), the common name and Subject Alternative Names (SANs) it covers, the certificate chain, and whether the certificate is currently valid.
What are Subject Alternative Names (SANs)?
SANs are the list of hostnames a single certificate is valid for. A certificate issued for example.com might also cover www.example.com, mail.example.com, and api.example.com in its SAN list. Modern certificates use SANs rather than the older Common Name field, and browsers require the hostname to appear in the SAN list for the certificate to be trusted.
What is a certificate chain?
A certificate chain links the server's certificate to a trusted root certificate via one or more intermediate certificates. Browsers and operating systems maintain a list of trusted root Certificate Authorities. The server must send its certificate plus any intermediate certificates so that the client can build a complete chain of trust up to a root it recognises. A missing intermediate causes SSL errors even when the certificate itself is valid.
How far in advance should I renew an SSL certificate?
Most Certificate Authorities recommend renewing at least 30 days before expiry. Free certificates from Let's Encrypt expire after 90 days and are designed for automated renewal via tools like Certbot. Commercial certificates are commonly issued for one year. Letting a certificate expire causes browsers to show a full-screen security warning and blocks access for most visitors.
What is HSTS and how does it relate to SSL?
HSTS (HTTP Strict Transport Security) is an HTTP response header that tells browsers to always connect to a site using HTTPS, even if the user types the HTTP address. It is set after the SSL certificate is confirmed valid. Once a browser sees an HSTS header, it refuses to connect over plain HTTP for the specified duration, protecting against SSL-stripping attacks.
What is a wildcard SSL certificate?
A wildcard certificate covers a domain and all its first-level subdomains using an asterisk in the common name (e.g. *.example.com). It is valid for www.example.com, api.example.com, etc., but not for the root domain example.com or second-level subdomains like a.b.example.com unless they are explicitly listed in the SAN field.
Can I check the SSL certificate of an IP address directly?
Yes, if the server presents a certificate when contacted on port 443. However, without a matching domain name in the SNI (Server Name Indication) extension, the server may return a default certificate rather than the one for a specific virtual host. Enter the domain name rather than the IP address to get the certificate for a specific site.