Decode certificates, CSRs and keys
For checking what a certificate authority sent you, what a server bundle contains, or which key belongs to which certificate, without pasting anything secret into someone else’s website. Everything is read inside this tab: the page works with the network off, and the CRL and OCSP addresses in a certificate are shown as text, never contacted.
- Runs entirely in your browser
- Works offline
- No upload
- No sign-up
- No watermark
Loading the tool…
How it works
- Paste one or several PEM blocks (-----BEGIN CERTIFICATE----- and so on), or drop .pem, .crt, .cer, .der, .csr or .key files.
- Read each item: names, validity with the days left, extensions, fingerprints. For a chain, the page shows which certificate signed which and whether the order is right.
- Check whether a key or CSR belongs to a certificate, and download any item as PEM or DER.
Why nothing is uploaded
Every operation on this page is done by code running inside your browser tab, using the same engine that renders web pages. The file is read from disk into your tab’s memory, transformed there, and written back out as a download. It is never sent anywhere — not to us, not to a third party.
Verify it yourself
- Open your browser’s developer tools (F12) and select the Network tab.
- Load your file and run the tool.
- The only requests you will see fetch the tool’s own code — and, for a few heavy tools, their open-source engine (also from this site) or an AI model from Hugging Face — plus one small page-view ping to loreatec.jp (page address and title, nothing more). None of them carry your file.
Frequently asked questions
Is it safe to paste a private key here?
The key never leaves this tab: there is no upload, and the page works with the network disconnected. Only the key type and size are shown, never the key itself. That said, you only need the key to check that it matches a certificate; for everything else, a certificate or a CSR is enough.
How does it know whether a key belongs to a certificate?
It compares public keys. A certificate and a CSR carry the public key. For a private key the page does not rely on the copy of the public key that the file may store: it works the public key out from the secret part (for RSA it checks with exact arithmetic that the two primes multiply to the modulus and that the exponents fit together; for EC and Ed25519 it calculates the public key from the secret). When two items have the same public key they belong together, and the page says so next to each one. If the public key stored in a key file does not match its secret part, the page says the file is inconsistent and reports no match; if this browser cannot do the calculation, it says that the match cannot be checked.
Does it check revocation or trust?
No. Checking revocation means contacting the certificate authority’s CRL or OCSP server, which would tell it what you are looking at; the addresses are shown so you can check them yourself. The page verifies the signatures between the certificates you give it, but it does not decide whether the root is trusted by browsers.
Which formats does it read?
PEM text with one or many blocks (certificates, CSRs, public keys, PKCS#8, PKCS#1 and SEC1 private keys, encrypted PKCS#8 keys with their passphrase) and binary DER files. PKCS#12/PFX files are recognised but not opened; the page shows the OpenSSL command that extracts their parts. A damaged or cut-off file gets a message saying where it breaks.