Protocols
Saved & recent

Certificate

Also called: digital certificate, X.509 certificate

A digital certificate binds a public key to a named subject under an issuer’s signature. In the X.509 format used by many TLS deployments, it also carries validity dates and constraints on how the key may be used. The public certificate can be shared; the corresponding private key must remain protected.

For example, a server presents a certificate for api.example.com. A client checks the name and other applicable requirements, including a valid path to a trusted issuer. Merely receiving a certificate is insufficient, and the certificate alone cannot prove the presenter possesses the private key.

Related
Certificate authority, TLS handshake, Mutual TLS
Further reading
public certificate subject · shop.example.com public key validity interval issuer signature protected endpoint store private key handshake possession proof verified with the certified key
The public certificate binds a name and public key under an issuer’s signature. The private key stays separate. Certificate validation and proof of private-key possession are both needed for the illustrated TLS authentication.

View in the full Protocols collection