Free tool
SSL Certificate Checker
A live TLS handshake with the server, not a cached report: who issued the certificate, which names it covers, when it expires and whether browsers trust it today.
What the checker inspects
The tool performs a real TLS handshake on port 443 with SNI, exactly like a browser, and reads the certificate the server presents: subject and issuer, validity window with a day countdown, every hostname in the Subject Alternative Name list, the negotiated protocol and cipher, the signature algorithm, and the length of the chain the server sent. Verification runs first with the standard trust store, so “trusted” here means trusted by real browsers, not merely present.
The three failures that matter
Expired is binary: past the date, every visitor gets a warning page. Name mismatch means the certificate does not cover the hostname being visited; it usually appears after domain or CDN changes. Broken chain is the sneakiest: the site works in browsers that cached the intermediate certificate and fails everywhere else, which makes it look intermittent. The report distinguishes all three so you fix the right thing.
Certificates during migrations
Every site move risks a certificate gap: the new server answers before its certificate is issued, or the old wildcard does not cover the new subdomain. Our migration checklist issues and verifies the new certificate before DNS switches, so visitors never see the gap. If you are planning a move, this checker plus our DNS lookup covers the two failure points that cause almost all launch-day outages.
Frequently asked questions
What does "not trusted" mean if the site seems to work?
The certificate failed verification from a neutral client: it may be self-signed, expired, or the server may be missing intermediate certificates in its chain. Your browser might still open the site because it cached the intermediates from another visit, but many visitors, and most crawlers and APIs, will see a security error.
How early should I renew a certificate?
Treat 30 days as the alarm threshold, which is why the report turns amber there. Modern certificates from Let's Encrypt renew automatically every 60-90 days; if your expiry is drifting close, the automation is broken and will fail silently at the worst moment.
Does the certificate affect SEO?
HTTPS has been a confirmed (light) ranking signal since 2014, but the real damage from a broken certificate is blunter: browsers show a full-page warning, visitors leave, and Chrome marks the site "Not secure". An expired certificate is a conversion catastrophe long before it is an SEO problem.
What is a wildcard certificate and does a name mismatch matter?
A wildcard like *.example.com covers one level of subdomains. A mismatch means the certificate exists but was issued for different hostnames, so browsers refuse it for this address; the classic case is a certificate covering www.example.com being served on the bare domain, or vice versa.
Ready to get an exact copy of any website?
Send us a link and get a free, no-obligation estimate within one business day.
Get a free quote