Private Key Checker
Validate an RSA, named-curve EC or Ed25519 private key and compare its public fingerprint with a certificate, CSR or public key on your device.
Check That a Private Key Matches a Certificate
Private Key Checker: how to use it
- Open a private key file or paste its PEM block. Choose Run matching example to generate and check a disposable test pair.
- To verify a pairing, also supply one X.509 certificate, PKCS #10 certificate request or SPKI public key.
- Choose Check private key. Read the signing check and compare the SHA-256 public fingerprints. Use Clear to discard the inputs.
Limits and notes
Reads one unencrypted PEM or DER key and one optional public document, up to 64 KiB each. Supports PKCS #8 RSA, P-256, P-384, P-521 and browser-supported Ed25519, plus two-prime PKCS #1 RSA and named-curve SEC 1 EC. It checks a local signature and compares public keys. Reports contain public facts, and inputs stay in tab memory.
How your privacy works →Private Key Checker: common questions
Which fingerprint does the checker show?
It hashes the DER SubjectPublicKeyInfo with SHA-256. A certificate fingerprint covers the certificate as a whole and uses different bytes.
Can a matching key tell me whether a certificate is trusted?
A match identifies the same public key. Certificate trust, expiry and domain identity require separate checks against the intended platform and hostname.
Does the checker accept an encrypted or OpenSSH private key?
The supported inputs are unencrypted PKCS #8, PKCS #1 RSA and named-curve SEC 1 EC. Keep protected keys in your normal local key-management workflow.