KitWharfFREEFast & Private Web Apps

How to Decode X.509 SSL Certificates (PEM vs. DER), Check Expiry & Audit SANs Locally

November 17, 20268 min readKitWharf Team
Interactive Online Tool Available

X.509 SSL Certificate PEM/DER Decoder & Expiry Inspector

Decode PEM, CRT, CER, and binary DER certificates locally in browser RAM. Inspect SANs, expiry countdown, key strength, SHA-256 fingerprints, and convert PEM to DER.

Launch Free Tool

Why Inspecting Internal Certificates Locally Matters

When debugging TLS handshakes on internal Kubernetes ingress controllers, private Active Directory CAs, or staging load balancers, you often need to inspect a .pem, .crt, .cer, or binary .der file quickly.

Pasting internal corporate certificates into random cloud SSL decoders leaks internal hostnames (*.internal), organizational units, and private infrastructure topology. With KitWharf's X.509 SSL Certificate Decoder, the entire RFC 5280 ASN.1 parser runs inside your browser's JavaScript memory—zero network uploads, zero logging.


PEM vs. DER vs. CRT vs. CER: Quick Format Cheat Sheet

Extension / Format Encoding Multi-Cert Chain? Typical Environment
PEM (.pem) Base64 ASCII + -----BEGIN CERTIFICATE----- Yes (fullchain.pem) Nginx, Apache, Kubernetes, OpenSSL
DER (.der) Raw Binary ASN.1 No (Single cert) Java KeyStores, Windows, Embedded IoT
CRT (.crt) Usually PEM (sometimes DER) Possible Linux / macOS trust stores
CER (.cer) Either PEM or Binary DER No Windows IIS / CryptoAPI

You can drop any of these formats into the X.509 SSL Certificate Decoder—it auto-detects binary DER vs. PEM text and lets you convert and download between .pem and .der in one click.


5 Things Every SysAdmin Should Audit Before Deploying a Cert

  1. Expiry Countdown & Validity Window: Verify both notBefore and notAfter in UTC. Publicly trusted TLS certificates are capped at 398 days (and moving shorter), while internal CAs should still be monitored for 30-day renewal alerts.
  2. Subject Alternative Names (SANs): Modern browsers ignore Common Name (CN). Confirm every required DNS hostname, wildcard (*.domain.com), or IP address is listed under SANs.
  3. Key Size & Signature Algorithm: Ensure RSA keys are at least 2048-bit (or ECDSA P-256 / P-384) and signed with SHA-256 / SHA-384—never deprecated SHA-1 or MD5.
  4. Basic Constraints & Key Usage: Confirm leaf server certs have CA: FALSE with TLS Web Server Authentication Extended Key Usage, while Intermediate CAs have CA: TRUE.
  5. SHA-256 Fingerprint & Chain Order: Use the multi-cert chain tabs to verify that Leaf, Intermediate, and Root certificates match expected thumbprints.

Pre-Issuance vs. Post-Issuance: Using CSR & Certificate Decoders Together

  • Before ordering a certificate: Run your .csr through the KitWharf SSL CSR Decoder to verify Subject DN fields, SANs, and key bit length.
  • After the CA issues the certificate: Drop the returned .pem, .crt, or .der into the KitWharf X.509 SSL Certificate Decoder to confirm expiry dates, chain completeness, and fingerprints before reloading Nginx or HAProxy.
Found this guide helpful? Share it with your team:

Ready to put this into practice?

Launch our free X.509 SSL Certificate PEM/DER Decoder & Expiry Inspector — instant client-side execution in your browser with zero registration required.

Open Tool