Inspect the structure of PEM-encoded blocks — labels, payload, chain ordering — and learn the certificate formats. Nothing is validated against a trust store.
Waiting for a PEM block
Anything between -----BEGIN …----- and -----END …-----.
Waiting for a PEM block
Certificates, keys and CSRs are all read.
PEM Text Inspector runs entirely on your device — nothing is uploaded, and no certificate is checked against a trust store.
You’re on the Free plan. Compare plans
Certificate problems are usually not cryptographic. They are a file in the wrong format, a chain in the wrong order, or a private key where a certificate should be — and all three are visible in the PEM text itself.
Chain order is the one that breaks TLS handshakes for some clients and not others. The server certificate must come first, then each issuer in turn. Browsers often paper over a wrong order by fetching the missing issuer themselves; many non-browser clients do not, which is why an API call fails while the site loads fine in Chrome.
A private key among the certificates is flagged loudly, because `fullchain.pem` and `privkey.pem` get concatenated by accident more often than anyone admits. **If a private key has been pasted anywhere outside your own machine, treat it as compromised and reissue it.** Nothing here uploads it, and that advice stands regardless.
The format vocabulary is laid out, since it is genuinely confusing. PEM is base64 with header lines; DER is the same data as raw bytes. `.crt`, `.cer` and `.pem` may each be either. PKCS#12 (`.p12`, `.pfx`) is a password-protected bundle, and PKCS#8 is the modern private key wrapper whose header says `PRIVATE KEY` where the older forms name the algorithm.
**Nothing is validated.** The base64 is decoded enough to confirm it is well-formed, and no certificate is parsed as X.509, checked against a trust store, or tested for expiry. Telling you whether a certificate is valid requires a trust decision this tool deliberately does not make.
No, and it does not try. Validity means a trust-store check, an expiry check and name matching against the host — all of which need context this tool does not have. It reads the PEM structure only.
Server certificate first, then each issuer up the chain. Browsers often recover from a wrong order by fetching the missing issuer; many API clients do not, which is why the site works and the integration does not.
The same data in two encodings — DER is raw bytes, PEM is DER base64-encoded with `-----BEGIN-----` header lines. The file extension tells you little: `.crt` and `.cer` can be either.
Treat it as compromised and reissue it. Nothing here uploads, logs or stores it, but a key that has been in a clipboard, a browser or a chat window should not stay in service.
It is a chain — the server certificate followed by its issuers. Some files also include the private key, which is convenient for a server and means the file must be protected like a key, because it is one.