Use a leaf certificate or fullchain copied from a file, vendor portal, or ticket.
PEM decoder
Decode a certificate file without touching the server.
Use this when you have a public certificate file, vendor-provided fullchain, or internal/private certificate evidence and need to understand what it contains before deployment or handoff.
Decoder workspace
Decode a PEM certificate or fullchain
Paste public certificate PEM blocks to inspect identity, SANs, validity, key, extensions, and fingerprints without probing a hostname.
Paste one certificate or a fullchain PEM. Private keys are rejected and should never be pasted into this tool.
Review subject, issuer, SANs, validity, serial number, key, and extensions.
Use SHA fingerprints and serial numbers to compare certificate versions.
After deployment, run the public checker to confirm customers receive the expected certificate.
Decoder intent
Use this before the certificate is live or when the endpoint is private.
The PEM decoder is for certificate-file review and handoff work. It answers what a certificate contains, which names it covers, and which identifiers prove whether two PEM files are the same.
Inspect certificate files and fullchains
A hostname probe only works when the certificate is already live and publicly reachable. The decoder handles the earlier workflow: paste a public PEM block and inspect the certificate before it is served.
- Decode a leaf certificate before installing it.
- Decode a fullchain to review leaf and intermediate order.
- Decode internal or private certificate evidence without exposing private keys.
Read identity and extension fields
The decoded result shows the fields teams usually need for renewal reviews, support tickets, and vendor handoffs: subject, issuer, SANs, serial number, validity, key algorithm, key usage, extended key usage, CA flag, and fingerprints.
- Use SANs to confirm hostname and wildcard coverage.
- Use serial number and fingerprints to compare versions.
- Use key usage and EKU to catch certificates that are not appropriate for TLS server use.
Keep private keys out of the workflow
The decoder is intentionally certificate-only. It rejects private key PEM blocks because key material should not be pasted into browser tools, support tickets, or chat threads.
- Paste only BEGIN CERTIFICATE blocks.
- Use the decoded report for tickets and inventory notes.
- Use the live checker after deployment to confirm the public endpoint serves the expected certificate.
A decoder identifies the file. Monitoring remembers what went live.
Use the decoder before deployment, then add monitoring when issuer, SAN, fingerprint, or expiry changes should stay visible on the public endpoint.
What does the certificate decoder show?
It decodes public X.509 certificate fields from pasted PEM blocks, including issuer, subject, SANs, serial number, validity dates, signature and key details, extensions, and SHA-1/SHA-256 fingerprints.
Can I decode a certificate before it is live?
Yes. Paste the public certificate or fullchain PEM and the decoder inspects the file locally in the browser without connecting to the hostname.
Can I paste a private key?
No. The decoder rejects private key PEM blocks. Use only public certificate blocks and keep private keys inside your certificate manager or server environment.