SSL Certificate Inspector
Decode a certificate or CSR, convert PEM/DER, check a certificate against its private key, generate a CSR, and probe a host's TLS.
What this certificate inspector does
Decode an X.509 certificate or a certificate signing request, convert between PEM and DER, check whether a certificate and a private key belong together, generate a CSR, and inspect what a host actually presents over TLS. A browser cannot read the certificate a TLS handshake returns, so this is a server-side tool and says so.
How to use it
Choose an action. decode, pem-to-der, der-to-pem and key-match read the certificate field (PEM, or base64 DER); key-match also needs the private key. csr-parse reads the CSR field, while csr-generate builds a new RSA key and CSR from the common name and subject alternative names. tls connects to the host on port 443 and reports the leaf certificate, negotiated version and cipher; versions tries each TLS version separately.
Privacy and safety
The values you paste are sent to the tool server for that run and are not stored. Private keys pasted for key-match are used only for the comparison, and the key generated by csr-generate is returned once and never persisted. Host probes refuse private and reserved addresses, and the page does not claim the work happens locally.
Decode a certificate or a CSR, convert between PEM and DER, check that a certificate matches a private key, generate a CSR or a self-signed certificate, or probe a host's TLS from the tool server.
The probe opens its own connection to port 443 and reads what the server presents: the leaf certificate, the negotiated protocol version and the cipher. A browser can show you a lock and its own certificate panel, but it does not hand a web page the peer certificate, the chosen cipher or a test of obsolete protocol versions; this page gets those from the server side instead.
The certificate report includes the subject, issuer, serial, validity dates, days remaining, subject alternative names, key type and size, signature hash, CA flag and a SHA-256 fingerprint. Nothing is signed or certified here: the page decodes what you paste and never claims a certificate is trusted.
Local decoding and conversion
Decode, pem-to-der, der-to-pem, key-match, csr-parse and csr-generate work on values you paste. A PEM body that lost its line breaks is re-wrapped before parsing, and a value that is neither PEM nor base64 DER is refused with a sentence rather than a parser error.
Key-match compares the public key derived from the certificate with the public key derived from the private key and reports whether they are the same key, plus the key type of each. The private key is sent to the server for that run, so the page does not repeat the browser converter's local-only promise.
- Certificate and CSR: PEM or base64 DER
- Conversions: PEM to DER, DER to PEM, PFX to PEM, PEM to PFX
- Generation: CSR or self-signed, RSA 2048, 3072 or 4096
What the network probes read
The versions action attempts TLS 1.0, 1.1, 1.2 and 1.3 one at a time and reports which negotiated. A refused attempt can mean the server does not support that version or that the server-side TLS stack declined to offer it, so the result is evidence rather than a scanner verdict.
The CRIME and POODLE probes build a ClientHello by hand, so a modern local policy cannot hide a server that still accepts TLS compression or TLS 1.0 with CBC ciphers. Heartbleed is not tested: it needs a full handshake with a negotiated heartbeat extension, which this page does not perform.
- TLS: certificate, version and cipher on port 443
- Versions: four attempts, each reported separately
- CRIME and POODLE: hand-built ClientHello probes
How to use the actions
Pick one of the fourteen actions, paste the certificate, key, CSR or host it asks for, and press Run; the choice decides which fields appear. Decoding and conversion read pasted PEM or base64 DER, key-match takes the certificate with its private key, and the TLS, versions, CRIME and POODLE actions take a hostname probed on port 443.
Read the report the action names: decoded fields with the SHA-256 fingerprint, a match verdict with both key descriptions, or one record per TLS version attempted. A pasted private key travels to the server for that run, so treat it as exposed afterwards.
What to Expect
Best for
- Reading the fields of a certificate or CSR
- Checking that a certificate and a key belong together
- Seeing which TLS versions a host accepts
Not ideal for
- A trust or compliance audit, which needs a full scanner and a policy
- Proving a server is safe, since the probes cover specific weaknesses only
- A browser's own view of a certificate, which this page cannot read
What this tool keeps
- Every decoded field, including the SHA-256 fingerprint
- One result per TLS version attempted
- The selected cipher and compression value from a probe
What may need cleanup
- A refused TLS version, which may be the server's policy or this server's stack
- The CRIME and POODLE readings, which are specific probes rather than a grade
- A private key pasted for key-match, which should be treated as exposed to this run
Common errors
- Reading a failed TLS 1.0 attempt as proof the server supports it
- Expecting Heartbleed coverage from the CRIME and POODLE probes
- Pasting a private key into key-match and assuming it stayed in the browser
Example use cases
- Checking a certificate's expiry and SANs
- Confirming a key pair before installing a certificate
- Seeing whether an old host still negotiates TLS 1.0
Sample input
A PEM certificate and its private key pasted into key-match, followed by a versions check on example.com.
Sample output
A match verdict with both key descriptions, then four version records naming the negotiated cipher or the error class for each attempt.
Who this is for
- System administrators
- Developers configuring TLS
- Security learners reading certificate fields
Frequently asked questions
What does the certificate inspector read?
A certificate or CSR's decoded fields, a PEM or DER conversion, a key match, a generated CSR or self-signed certificate, and network probes of a host's TLS.
Is it a trust or compliance audit?
No. The probes cover specific weaknesses only and do not prove a server is safe.
Is a private key I paste for a key match exposed?
It is sent to this run, so treat any pasted private key as exposed to the tool server.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.