Check whether a TLS certificate and a certificate signing request belong to the same key pair. The process is straightforward, transparent, and built for everyday trust decisions — no account, no upload, no waiting.
Runs entirely in your browser — nothing you paste or upload is sent anywherePaste the PEM contents or upload files for both the TLS certificate and the CSR. When you click Validate, the tool compares the public keys and presents the key details side by side.
The validator focuses on the public key relationship between the certificate and the CSR. When the cryptographic material matches, the certificate was created from the same private key that generated the request.
Every TLS certificate is part of a chain of trust. When a website or service uses a certificate, it is important to confirm that it was issued from a legitimate request and that the private key remains under the control of the expected owner.
This page is a simple safety check for digital certificates. It helps people confirm whether a certificate and a request are truly connected — useful for internal audits, service migrations, and everyday certificate housekeeping, without needing to dive into low-level security jargon.
This kind of verification is valuable for developers, administrators, operations teams, and anyone helping maintain secure online services. The goal is not to sell a service, but to make certificate validation easier to understand and easier to trust.