domhaul logodomhaul

SSL Certificate Checker

Enter a domain to check its SSL (TLS) certificate. Two answers come back. Live: one HTTPS request to the name from a Cloudflare data center, which fails the way a browser does on an expired, self-signed, wrong-name or incompletely chained certificate. On record: the newest unexpired certificates issued for the name, from the Certificate Transparency logs where every publicly trusted certificate has to be published, with the issuer, issue and expiry dates, days left and every name covered. On 17 November 2026 all 25 well-known sites we checked passed; of the 12 below, example.com's certificate was the closest to expiring, at 38 days, and 9 run on certificates of 100 days or less.

Free, no sign-in, 20 checks a minute. One HTTPS request to the name you enter, on port 443; private and local addresses are refused. Also: Redirect checker, HTTP header checker, Website down checker, IP lookup.

SSL certificates of well-known sites

Checked on November 17, 2026 through this tool's own API, from Cloudflare SJC. Click a site to run it live.

SiteIssuerIssuedExpiresDays leftLifetimeNames
google.comGoogle Trust ServicesNov 16, 2026Feb 8, 20278284 days519, wildcard
github.comSectigo LimitedOct 30, 2026Jan 27, 20277190 days2
amazon.comAmazonNov 13, 2026May 29, 2027193198 days24
apple.comApple Inc.Nov 16, 2026Feb 11, 20278687 days1
microsoft.comMicrosoft CorporationOct 22, 2026Jan 30, 202773100 days193
wikipedia.orgLet's EncryptOct 4, 2026Jan 2, 20274690 days41, wildcard
cloudflare.comGoogle Trust ServicesNov 16, 2026Feb 14, 20278990 days2, wildcard
netflix.comDigiCert IncNov 16, 2026Feb 14, 20278891 days15
youtube.comGoogle Trust ServicesNov 16, 2026Feb 8, 20278284 days519, wildcard
bbc.co.ukGlobalSign nv-saNov 11, 2026May 29, 2027192199 days22, wildcard
stripe.comDigiCert, Inc.Nov 16, 2026Jun 2, 2027197199 days2, wildcard
example.comSSL CorporationSep 26, 2026Dec 25, 20263890 days2, wildcard

The newest unexpired certificate on record for each name, from Certificate Transparency logs through Cert Spotter; a server may still be presenting the one before it. Lifetime runs from issue to expiry; since 15 March 2026 no public certificate may run past 200 days.

SSL Certificate Checker questions

How do I check when an SSL certificate expires?

Enter the domain above: the expiry date and the days left are at the top of the result. In a browser, click the icon left of the address and open the certificate details. On a command line, openssl s_client -connect example.com:443 -servername example.com | openssl x509 -noout -dates prints the dates of the certificate the server presents right now, which is the one that counts if it differs from the newest on record. Renew with 30 days to spare, which is when Let's Encrypt's clients and most hosting panels renew on their own; this checker warns when the newest certificate has under 14 days left and nothing newer has been issued.

Why do SSL certificates expire so fast now?

Because browsers and certificate authorities voted to shorten them. Under CA/Browser Forum ballot SC-081 (April 2025), a public TLS certificate could run at most 398 days until 15 March 2026, 200 days since then, 100 days from 15 March 2027 and 47 days from 15 March 2029, so renewal has to be automated. The 12 certificates below already show it: the three longest (amazon.com, bbc.co.uk and stripe.com, 198 to 199 days) sit just under the 200-day cap, and the other nine run 84 to 100 days, Google's own the shortest at 84.

What is Certificate Transparency?

A set of public, append-only logs of issued certificates. Chrome has refused publicly trusted certificates that are not logged since 30 April 2018, and Apple since October 2018, so the logs hold every certificate a browser will accept for your domain, including any you did not ask for: that is how mis-issued certificates get caught. This checker searches them through crt.sh and Cert Spotter. Busy names carry a lot: on 17 November 2026, 448 unexpired certificates named youtube.com and 272 named google.com, the newest of them a shared Google certificate with 519 names on it.

Why does my browser say Your connection is not private?

The certificate failed one of the browser's checks, and the error code says which. NET::ERR_CERT_DATE_INVALID: expired or not yet valid, or your device's clock is wrong. NET::ERR_CERT_COMMON_NAME_INVALID: it does not cover the name you typed, often www against the bare domain. NET::ERR_CERT_AUTHORITY_INVALID: self-signed, from an untrusted issuer, or missing its intermediate certificate. If this checker passes a site your browser rejects, look at your side: antivirus or a company network that inspects HTTPS, or the clock. The four badssl.com test sites for those faults all failed here on 17 November 2026 while CT logs showed a valid certificate for each name: the logs record what was issued, the live check what the server presents.

More free website and domain tools

The redirect checker follows a URL through every 301, 302, 307 and 308 to the page that answers. The HTTP header checker shows the response headers a URL sends and grades its six security headers. The website down checker checks from outside your network whether a site answers, and how fast. The IP lookup shows who owns an IP address or hosts a site, with its network, ASN and reverse DNS. When a name does not resolve at all, the DNS lookup, the DNS propagation checker, the CNAME lookup and the Nameserver lookup show what its DNS says. For who owns a domain and when it expires, use the WHOIS lookup; to find a name that is still free, the domain availability checker.