X.509 certificate
What is X.509 certificate?
An X.509 certificate is the standardized data structure, defined in RFC 5280, that binds a public key to an identity and is signed by the certificate authority that issued it. Every TLS certificate AdminKit's SSL/TLS check tool inspects is an X.509 certificate, carrying a subject, issuer, validity period and Subject Alternative Name list.
By AdminKit team, Netbase JSC · Updated
An X.509 certificate is the standardized data structure, defined in RFC 5280 (current document status at its IETF Datatracker entry), that binds a public key to an identity — typically a hostname — and is signed by the certificate authority that issued it. Every TLS certificate a browser or mail server checks is an X.509 certificate: it carries a subject, an issuer, a validity period, the public key itself, a Subject Alternative Name (SAN) list of the hostnames it actually covers, and extensions like key usage that constrain what the certificate may be used for. To read those fields directly, OpenSSL’s x509 command is documented as a multi-purpose certificate handling command that can print certificate information, convert certificates to various forms and sign certificates.
The format predates the web — it was originally designed for the X.500 directory standard — but RFC 5280 profiles it specifically for internet PKI use, which is why nearly every modern certificate, regardless of the CA that issued it, follows the exact same field layout a client can parse and validate the same way. The CA/Browser Forum’s Baseline Requirements build on top of RFC 5280’s format, adding the industry-agreed rules — validity period limits, required extensions, revocation checking — that a publicly-trusted CA must follow when issuing one.
AdminKit groups x.509 certificate under its machine protocols cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
Did X.509 originate with the web?
No -- the format predates the web; it was originally designed for the X.500 directory standard. RFC 5280 later profiled it specifically for internet PKI use.
What fields does every X.509 certificate carry?
A subject, an issuer, a validity period, the public key itself, a Subject Alternative Name (SAN) list of the hostnames it actually covers, and extensions like key usage that constrain what the certificate may be used for.
Why do certificates from different CAs look the same structurally?
Because nearly every modern certificate, regardless of the issuing CA, follows the exact same RFC 5280 field layout, which is what lets a client parse and validate any of them the same way.
What adds rules beyond RFC 5280's base format?
The CA/Browser Forum's Baseline Requirements build on top of RFC 5280's format, adding industry-agreed rules -- validity period limits, required extensions, revocation checking -- that a publicly-trusted CA must follow when issuing one.