SSL Audit Checklist

An SSL certificate is one of the most visible trust signals on a website. When it is valid and properly configured, visitors see a padlock and trust the site. When it is expired or misconfigured, browsers show a full-screen warning that most visitors will not click through.

SSL issues are common across client portfolios. Auto-renewal fails. Hosting migrations break certificate chains. Wildcard certificates do not cover every subdomain. A structured SSL audit catches these issues before they affect visitors.

Work through this checklist for each domain in scope. Include all subdomains that are client-facing or process sensitive data.

• SSL certificate is currently valid (not expired)
• Certificate expiration is more than 60 days away (flag as warning if less)
• Certificate expiration is more than 30 days away (flag as critical if less)
• Certificate is issued to the correct domain (exact match or wildcard coverage)
• www and non-www variants are both covered by the certificate
• All relevant subdomains are covered (wildcard or individual certificates)
• Certificate chain is complete (all intermediate certificates installed)
• Certificate is issued by a trusted Certificate Authority (not self-signed)
• HTTPS is enforced: HTTP redirects to HTTPS on all checked URLs
• No mixed content (HTTP resources loaded on HTTPS pages)
• HSTS header is present and configured correctly
• Certificate renewal process confirmed (who renews, auto or manual?)
• Renewal reminder is in place (monitoring alert or calendar)

Certificates expiring within 30 days are a critical finding. Auto-renewal that has not run for any reason — billing lapse, DNS change, hosting provider issue — will leave the certificate to expire silently.

Incomplete certificate chains are common after hosting migrations. The certificate itself may be valid, but if intermediate certificates are not properly installed on the new server, some browsers will show a warning.

Wildcard certificates cover *.example.com but not example.com itself. If a client's wildcard was deployed without also covering the apex domain, visitors to the root domain may see an SSL warning.

Report SSL audit findings in plain language. "Your SSL certificate expires on [date] — please confirm your hosting provider will renew it automatically" is better than technical certificate details most clients cannot act on.

For issues requiring immediate action, communicate out-of-cycle. An expiring certificate inside 30 days is a priority communication, not a report footnote.

Document all SSL findings — including clean results — in your client record. When a certificate does eventually expire, your records will show when you first detected the approaching expiration.

MonitorMojo checks SSL certificate validity and expiration as part of every health check. You get certificate status, issuer, and expiration date alongside uptime, response time, and security headers — in a single check.

Use the expiration date in the check result to populate this checklist. If the expiration is within 60 days, flag it. If within 30 days, escalate. If already expired, contact the client immediately.

Historical SSL check data gives you a record of certificate status over time — useful documentation for conversations with clients or hosting providers.

SSL Audit Checklist is best understood as a repeatable website health workflow, not a promise that every outage or configuration issue will be avoided. A complete SSL audit checklist for checking certificate validity, expiration, configuration, and renewal processes for client websites.

In practice, this workflow centers on SSL certificate status, expiry windows, renewal ownership, and post-renewal verification. Each check is planning input: it can show that the site is reachable, that a certificate has a given expiry window, that response time has shifted, or that a header is missing. It cannot prove root cause by itself or replace a human response. The value is in making the review consistent enough that site owners and small teams can spot issues before someone downstream has to ask about them.

This is most useful for site owners and small teams. Agencies managing SSL certificates across multiple client websites

Beyond that primary audience, the same checks are reusable by anyone with a public-facing URL that matters to revenue, leads, or reputation: a recurring review is cheap insurance compared to hearing about the problem from a client or customer first.

Start by listing the URLs that actually matter instead of just the homepage — for a small team doing a routine check before something breaks in front of a visitor, that usually means the pages tied to revenue, signups, or trust, not every page on the site.

Next, define the check types for each URL: reachability, HTTP status, HTTPS/SSL certificate status and expiry window, response time, redirect behavior, and security header presence. For API, CLI, and AI-agent workflows, document which endpoint or command runs the check and where the result is stored.

Set a cadence that matches the risk — a low-traffic page may only need a monthly look, while a page tied to revenue or signups deserves a check after every deployment and before any campaign or launch.

Record what you find with a consistent format: URL, check type, status, issue, owner, detected date, and next review date. Then say what actually happened in plain language — a check can surface a symptom, but site owners and small teams still need to confirm the cause.

• Choose the URLs that matter most to visitors, clients, revenue, and operations.
• Run uptime, SSL, response time, and security header checks on a consistent schedule.
• Triage failed or risky checks by likely owner: hosting, DNS, SSL, code, platform, or third party.
• Record notes in a repeatable format so future reviews do not start from scratch.
• Send a plain-language summary with the issue, impact, owner, and next review date.
• Run a confirmation check after remediation so there is an external result to reference.

Use this template for recurring reviews: [URL], [Check Type], [Status], [Issue], [Priority], [Owner], [Detected Date], [Resolved Date], [Next Review Date]. Add a one-line summary at the top: what changed, what needs attention, and who owns the next step.

For site owners and small teams, group findings into the four signals that matter most: reachability, SSL status, response time, and security headers. Where nothing needs action, say the check found no issue in that area rather than implying full coverage.

• [URL]: the exact page or endpoint checked.
• [Check Type]: uptime, SSL, response time, headers, API, CLI, or agent workflow.
• [Status]: pass, review, failed, blocked, or needs human investigation.
• [Issue]: the observable symptom, not an unsupported root-cause claim.
• [Owner]: agency, developer, host, DNS provider, client, or third-party vendor.
• [Next Review Date]: when the team should confirm status again.

The most common mistake is monitoring only the homepage while a checkout, signup, or booking flow silently breaks. Another is assuming SSL auto-renewal always works — it can fail quietly, and an external check is the only way to catch that before a browser warning does.

For site owners and small teams specifically, the recurring miss is treating one clean check as proof the whole site is fine, or fixing an issue without ever writing down what happened — which means the next person repeats the same investigation from zero.

• Tracking too many low-value URLs while missing the ones that matter.
• Skipping notes after an issue is resolved.
• Reporting a status without an owner or next step attached.
• Assuming automation can resolve an incident without human review.
• Treating one clean check as proof that every risk is covered.

Consider a small team doing a routine check before something breaks in front of a visitor. A scheduled check flags that the site is slower than its usual baseline and that a security header is missing. Instead of guessing, the team logs the observation with a timestamp, assigns an owner, and re-checks after the fix ships — turning a vague "something feels off" into a specific, closed-loop task.

MonitorMojo runs website health checks that combine reachability, SSL certificate status, response time, and security header presence in one workspace, so this workflow doesn't require stitching together several separate tools.

The API and CLI make the same checks scriptable for site owners and small teams who want them wired into an existing process, while credit-based checks keep it practical to run reviews exactly when they matter — before a client call, after a deploy, or when someone asks whether the site is healthy. Results still depend on hosting, DNS, and how quickly the responsible team acts on what the check finds.