- What certificate formats are supported?
- The tool currently supports PEM (Privacy Enhanced Mail) format, which is the most common format for SSL/TLS certificates. PEM format uses Base64 encoding with -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- markers. If you have a certificate in DER format, you can convert it to PEM using OpenSSL: `openssl x509 -inform DER -in cert.der -out cert.pem`.
- What information can I see from a parsed certificate?
- Parsed certificates display comprehensive information: Subject (CN, O, OU, L, ST, C, E), Issuer (who issued the certificate), Validity Period (valid from/to dates), Public Key (algorithm, key size, modulus, exponent), Fingerprints (MD5, SHA1, SHA256), Serial Number, and Validity Status (valid/expired/not yet valid).
- How does certificate validity verification work?
- The tool checks if the current date is within the certificate's validity period (between validFrom and validTo dates). If the current date is before validFrom, the certificate is 'Not Yet Valid'. If after validTo, it's 'Expired'. If within the period, it's 'Valid'. The tool also calculates days until expiry to help plan certificate renewals.
- What are certificate fingerprints used for?
- Certificate fingerprints are cryptographic hashes (MD5, SHA1, SHA256) of the certificate content. They provide unique identifiers for certificates, enabling certificate pinning (associating specific certificates with domains), certificate verification, and detecting certificate changes. Fingerprints are commonly used in security configurations and certificate management systems.
- Can I parse certificate chains?
- The tool parses individual certificates. For certificate chains (leaf certificate + intermediate certificates + root certificate), you can parse each certificate separately by extracting them from the chain. Certificate chains are typically provided as multiple PEM blocks concatenated together.
- Is the certificate data sent to any server?
- No. All certificate parsing is performed entirely in your browser using client-side JavaScript. Certificate data never leaves your device and is not sent to any server. This ensures complete privacy and security for sensitive certificate information.