PEM Certificate and CSR Decoder

Read public PEM metadata from pasted text or a local file in a readable table.

On-device No sign-up Free to use

Inspect input controls

Showing an example. Edit to see your own.

Drop your file here

or choose one from your device

Choose one public certificate, CSR or public-key PEM file up to 360,000 bytes. The file replaces pasted PEM.

    ?

    One public PEM block only. Never paste a private key. The example is a synthetic self-signed certificate.

    Processed in your browser. Your inputs stay on this device.

    Result

    Showing an example.

    Decode the supplied example certificate’s public metadata; its self-signature is not verified.

    CERTIFICATE: public metadata decoded locally.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/pem-certificate-csr-decoder · 20 November 2026

    Was this helpful?

    How to use PEM Certificate and CSR Decoder

    1. Paste one supported public certificate, CSR or public-key block, or select a local UTF-8 PEM file.
    2. Keep private-key material out of this public metadata inspector.
    3. The metadata updates when you change the input. Read the decoded type, algorithm, names and dates alongside the checks this inspector does not perform.

    Example: PEM Certificate and CSR Decoder

    Decode the supplied example certificate’s public metadata; its self-signature is not verified.

    You add
    Public certificate, CSR or public-key PEM: -----BEGIN CERTIFICATE----- MIICjTCCAfagAwIBAgIBLDANBgkqhkiG9w0BAQsFADBiMSIwIAYDVQQDDBlzeW50 aGV0aWMuZXhhbXBsZS5pbnZhbGlkMRowGAYDVQQKDBFTeW50aGV0aWMgRXhhbXBs ZTELMAkGA1UEBhMCQkQxEzARBgNVBAgMClNvbWUtU3RhdGUwHhcNMjYxMDAzMDUz MDE4WhcNMjYxMTAyMDUzMDE4WjBiMSIwIAYDVQQDDBlzeW50aGV0aWMuZXhhbXBs ZS5pbnZhbGlkMRowGAYDVQQKDBFTeW50aGV0aWMgRXhhbXBsZTELMAkGA1UEBhMC QkQxEzARBgNVBAgMClNvbWUtU3RhdGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ AoGBAMeS8ZBQmrcWoZC3UUBnJY9CUsiMBwu2mTkv9LmR1DKV6jDhzkx+kpFCpsG8 2NNYnHjXdcyLfTh2S8H8xVVKX+M0bDMJavdRhaERBvofjNj2IGhT7nGtVZRPdX5E AnQvtB4zdtomwRd0W/C1kzl2dPHIsRjZCidBgn0svZqdBR1TAgMBAAGjUzBRMB0G A1UdDgQWBBSzAVyeN+I3JYpZQ34orllokcwc7TAfBgNVHSMEGDAWgBSzAVyeN+I3 JYpZQ34orllokcwc7TAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBCwUAA4GB AMCO0YpUfw8AGSiC5Td1rp2uVRmgAPW1vMyqKV0OxS/dDoSApfknGS3Q+8JrQTqJ ED6725YeVlSHqthpWzkggpCnOj3lXcx5D0YkrpV+m5I5XVKdu23rJArDj0FzOLKI Tuz33XCa2xRtHgZuwgHOpUfjzcRL3tNxU7VN/yewqd47 -----END CERTIFICATE-----
    You get
    CERTIFICATE: public metadata decoded locally.

    Options

    Local UTF-8 PEM file (optional)
    Choose one public certificate, CSR or public-key PEM file up to 360,000 bytes. The file replaces pasted PEM.
    Public certificate, CSR or public-key PEM
    One public PEM block only. Never paste a private key. The example is a synthetic self-signed certificate.

    Supported inputs and limits

    • One public certificate, PKCS#10 CSR, SPKI or RSA public-key PEM up to 256 KiB decoded;
    • DER depth 32 and 2,000 nodes.
    • RSA, P-256/P-384/P-521/secp256k1 EC and Edwards public structures only.
    • Extensions report OIDs/critical flags/sizes, not complete interpretation.
    • Refuses private keys, malformed/trailing DER and unsupported structures.
    More details

    No signature, chain, trust, revocation, ownership or security-strength validation.

    A selected UTF-8 PEM file replaces pasted text and is bounded at 360,000 bytes.

    The metadata table does not add SAN interpretation, key matching or certificate trust verification.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Validity dates are fields rather than a trust decision

    A certificate can contain an apparently current date range and still be untrusted or revoked. This tool reads public DER structure; it does not verify the signature, chain, hostname, ownership or revocation status. A CSR similarly contains requested identity details, not an issued trusted certificate.

    Extensions are only partially described

    The output reports extension identifiers, critical flags and sizes rather than fully interpreting every extension. Do not treat an absent decoded name as proof that a restriction is absent. Private keys, trailing DER and unsupported structures are refused. Keep the report’s parsing scope separate from security-strength or compliance claims.

    Questions about PEM Certificate and CSR Decoder

    Does a valid date mean a certificate is trusted?

    No. Trust also requires verified signatures, chain and other checks outside this tool.

    Does a CSR prove the requested names belong to someone?

    No. Names in a request are unverified input.

    Can private-key PEM be decoded?

    No. Paste only the supported public material.

    Page updated · Project managed by Tony Hines · Report a problem with PEM Certificate and CSR Decoder