🔒
DevOps

SSL Certificate Validation

Decode SSL certificate details, verify the certificate chain, and check expiration dates to prevent outages.

When to Use This Workflow

Validate SSL/TLS certificates before deployment to catch expiration issues, chain problems, and configuration errors.

Workflow Steps

1

Base64 Encoder

Decode PEM-encoded certificate from Base64 to inspect raw certificate data

Open Tool →
Verification: Successfully decoded PEM content; verify BEGIN/END CERTIFICATE markers
2

JSON Formatter

Format and validate parsed certificate metadata (subject, issuer, SANs) as JSON

Open Tool →
Verification: Verify Subject CN matches your domain; check SAN list includes all subdomains
3

Timestamp Converter

Convert certificate notBefore/notAfter dates to verify validity period

Open Tool →
Verification: notAfter is at least 30 days in the future; notBefore is in the past

Download Workflow Template

Download JSON

Frequently Asked Questions

How often should I check SSL certificate expiration?

At minimum monthly, but ideally set up automated monitoring. Let's Encrypt certificates expire every 90 days. This workflow helps with manual spot-checks during deployment.

What does 'certificate chain incomplete' mean?

It means the server isn't sending intermediate certificates. Browsers may still work (they cache intermediates), but API clients will fail. Always include the full chain: leaf + intermediate(s).

How do I check SSL certificates from the command line?

Use: openssl s_client -connect domain.com:443 -servername domain.com | openssl x509 -text. This workflow provides a visual alternative for quick validation.

Related Topics

SSL certificate TLS validation certificate expiry HTTPS check certificate chain

More Workflow Templates