Domains
SSL readiness
SSL readiness is the maintained planning record for how a domain's certificate renewal path is handled.
Updated 24 July 2026
What it means
SSL readiness is the operational planning context around a domain's TLS certificate. It records how the certificate is managed, whether renewal is automated, when the path was reviewed, and what notes explain the setup. It is different from the technical SSL check, which observes the live certificate and its expiry.
Why it matters
Shorter certificate lifetimes make renewal paths more important. A team needs to know whether a certificate is handled by a host, CDN, ACME automation, a manual process, or an unclear owner. The readiness record helps the team spot planning gaps before the live expiry date becomes urgent.
How CertPilot uses the term
CertPilot records SSL readiness metadata on domains and still keeps technical SSL status based on live public checks. It does not issue, install, renew, rotate, or automate certificates. It does not configure Certbot, ACME, reverse proxies, CDNs, DNS providers, or hosting platforms.
What to record
- Certificate management method.
- Automation status and owner.
- Last readiness review date.
- Notes about hosting, CDN, or renewal path context.
What not to assume
- SSL readiness is not certificate automation.
- Planning metadata does not change live certificate status.
- A green readiness record does not prove future renewal will succeed.
How to use this term in a review
Use SSL readiness when you need a shared operating definition in a management report, access review, renewal review, domain review, or evidence-pack discussion. The goal is not to turn a glossary term into a control by itself. The goal is to make the scope, source, owner, status, date, and follow-up clear enough that a manager or client can understand what was reviewed and what still needs attention.
- Use the related pages to move from definition to workflow.
- Keep evidence wording precise and avoid audit, legal, or certification overclaims.
- Record limitations when the source is public, manual, customer-entered, or incomplete.