Prevent SSL outages

Avoid the full-page browser warning that appears when a certificate expires or does not match.

The challenge

  • Shorter certificate lifetimes mean more renewals
  • Certificates spread across CDNs, servers and SaaS
  • Renewal failures that go unnoticed

A practical plan

  1. Inventory every certificate with Certificate Monitoring
  2. Automate renewal (ACME/Let's Encrypt or your host's auto-SSL)
  3. Restrict issuers with a CAA record
  4. Re-scan after renewals to confirm the new certificate is installed

Who it is for

Anyone running websites, APIs or portals — especially across several hosts, CDNs and SaaS tools.

Outcomes

  • No surprise certificate expiries
  • Every certificate known and owned
  • Issuance limited to your chosen CAs

Checklist

  • Automatic renewal everywhere
  • No certificates under 21 days left
  • CAA lists only your CAs
  • HTTP redirects to HTTPS
  • HSTS enabled

Step-by-step plan

A realistic timeline for a small team.

Day 1
  • Inventory certificates for each domain
  • List anything expiring within 21 days
Week 1
  • Move manual renewals to automatic (ACME)
  • Fix name mismatches and missing intermediates
Week 2
  • Publish CAA records
  • Add HSTS once HTTPS works everywhere
Ongoing
  • Re-check after each renewal

Start with a free check

No account needed.

Questions

Why are certificates getting shorter?

Browser makers and CAs agreed to reduce maximum lifetimes in steps (200 days from March 2026, 100 days from 2027, 47 days from 2029) to limit the impact of compromised keys.

See where your domain stands

Free for up to 3 domains. No card, no installs.

Start free