example.com:443 Ready for 47-day certificates: renewal looks automated certificate example.com, issued by Cloudflare TLS Issuing ECC CA 3 (SSL Corporation) lifetime 90 days (2026-09-26 to 2026-12-25), 66 left renewal probably automated PASS 15 March 2026 (in force) max 200 days, ~ 3 renewals/yr Automated renewal absorbs it: about 3 renewals a year, none of them by hand. PASS 15 March 2027 max 100 days, ~ 6 renewals/yr Automated renewal absorbs it: about 6 renewals a year, none of them by hand. PASS 15 March 2029 max 47 days, ~12 renewals/yr Automated renewal absorbs it: about 12 renewals a year, none of them by hand. PASS Certificate lifetime: 90 days Already within the 100-day limit that applies from 15 March 2027. PASS Renewal automation: probably automated A 90-day certificate from SSL.com. Nobody renews certificates this short by hand for long, so a client is almost certainly doing it. PASS Renewal timing: 66 of 90 days left No renewal is due yet. INFO ARI renewal window: not available SSL.com offers ACME, but not through a public directory this checker can ask for renewal information. ARI is how a CA tells clients to renew early ahead of a revocation; without it, a mass revocation is a manual scramble. see https://kirkdiamond.com/guides/acme-renewal-information-ari PASS Edges: 2 addresses, one certificate Every address the name resolves to serves the same certificate, so the last renewal reached all of them. # every address for example.com 172.66.147.243:443 2026-09-26 to 2026-12-25 SSL.com 85CA6AB068E9BCCE <- this report 104.20.23.154:443 2026-09-26 to 2026-12-25 SSL.com 85CA6AB068E9BCCE <- this report [2606:4700:10::6814:179a]:443 not checked: this server has no IPv6 route [2606:4700:10::ac42:93f3]:443 not checked: this server has no IPv6 route reproduce: for ip in $(dig +short example.com A example.com AAAA); do echo "$ip $(echo | openssl s_client -connect "[$ip]:443" -servername example.com 2>/dev/null | openssl x509 -noout -enddate)"; done