Paste a private key and a certificate to instantly check whether they're a matching pair — the single most common cause of a botched TLS deployment is uploading the wrong key.
Your PEM-encoded private key — it never leaves your browser.
The certificate you're about to deploy alongside it.
A clear yes/no, comparing the public key modulus embedded in each.
Deploying a certificate with the wrong private key breaks TLS entirely — this check catches it before you push to production.
No — the comparison runs entirely client-side in your browser.
Yes — both RSA and ECC (P-256/P-384) key/certificate pairs are supported.
