Parsed versus verified
Parsed means the bytes were read as an X.509 certificate and the fields below were decoded. It says nothing about whether the certificate is genuine, who controls it, or whether you should trust it.
Verified is reported here only for one narrow check: whether the certificate’s signature is mathematically valid for a public key. That key is the certificate’s own (when it is self-issued) or the key of an issuer certificate you included in the same input. A valid self-signature only proves the certificate is internally consistent, because anyone can sign a certificate for any name with their own key.
This tool does not check: that the chain leads to a root in a trust store, whether the certificate or any issuer has been revoked (CRL or OCSP), whether the certificate matches a hostname, name constraints, path length and policy rules, or Certificate Transparency. The validity dates are compared with your device’s clock, which is an observation, not a validation.
What is shown
- Version, serial number, subject and issuer, valid-from and valid-until dates.
- Signature algorithm, public key algorithm and key details (RSA modulus and exponent, elliptic curve and point, Ed25519).
- Subject Alternative Names (DNS, IP, email, URI), including wildcard names and internationalised names decoded from Punycode. Key Usage, Extended Key Usage and Basic Constraints, plus other common extensions.
- SHA-256, SHA-1 and SHA-512 fingerprints of the whole certificate, and the SHA-256 of the public key (SPKI). Fingerprints need the browser’s Web Crypto API, which is available on HTTPS pages.
- Factual notes, for example: expired or not yet valid, MD5 or SHA-1 signatures, RSA keys shorter than 2048 bits, no Subject Alternative Name, an unrecognised critical extension, or a malformed serial number.
Formats and files
PEM text (one or many -----BEGIN CERTIFICATE----- blocks, with or without extra text around them) and binary DER files are supported. Bare Base64 is also accepted. PKCS#7 and PKCS#12 bundles, certificate requests, CRLs and public keys are recognised and named but not decoded in detail.
Private keys
If the input contains a private key, the tool tells you the key type and size and removes the key from the input box. It does not display, copy, export or store any part of the key, and the bytes are overwritten in memory after identification. A private key should not be pasted into any web page unless it is a throwaway test key; if you pasted a real one, treat it as exposed and replace it. Encrypted keys are identified but not decrypted.
Privacy
Parsing happens entirely in your browser and nothing you enter is sent over the network. Nothing you paste or open is uploaded, logged or saved, and it is gone when you leave the page. Downloaded summaries contain only what is displayed on this page.