Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is an X.509 Certificate?

X.509 is the standard format for public key certificates, binding a public key to a name through a certificate authority signature. It underpins TLS, code signing, and email security.

Illustration for the cybersecurity term X.509 Certificate
Home / Blog / Cybersecurity Terms / What Is an X.509 Certificate?
17 November 2026

What Is an X.509 Certificate?

What Is an X.509 Certificate?

X.509 is the format that almost every public key certificate in use today follows. Originally part of the ITU-T X.500 directory work in 1988 and now profiled for the internet by RFC 5280, it defines a signed data structure that binds a public key to an identity. When your browser confirms a site, when Windows accepts a driver, or when a VPN authenticates a client, an X.509 certificate is what is being checked.

What Is Inside One

A certificate has three parts: the to-be-signed body, the signature algorithm identifier, and the signature itself. The body contains:

The Extensions That Actually Matter

ExtensionWhat it controls
Subject Alternative NameThe domain names and IP addresses the certificate is valid for. Browsers have ignored the common name since Chrome 58 in 2017, so a missing SAN means failure
Basic ConstraintsWhether this is a CA certificate and how deep the chain below it may go
Key Usage and Extended Key UsageWhether the key may sign, encrypt, authenticate a server, sign code, or issue timestamps
Authority and Subject Key IdentifierHints that let a verifier build the chain efficiently
CRL Distribution Points and Authority Information AccessWhere to fetch revocation data and the issuing certificate
Name ConstraintsLimits a subordinate CA to specific domains—the single most useful control for a private CA
Signed Certificate TimestampsProof of submission to Certificate Transparency logs

Encodings and File Formats

The structure is defined in ASN.1 and serialised with Distinguished Encoding Rules, giving a binary DER file. PEM wraps that binary in Base64 between BEGIN and END markers, which is what most Linux tooling expects. PKCS#12, with a .pfx or .p12 extension, bundles a certificate with its private key and chain under a password, and is what Windows and Java estates usually exchange. PKCS#7 carries certificates without keys. A surprising share of deployment incidents come from giving a service the wrong one of these, or from a chain file assembled in the wrong order.

How Validation Works

  1. Build a path from the presented certificate to a trusted root, using the issuer names and key identifiers.
  2. Verify each signature up the chain and check that every intermediate is marked as a CA.
  3. Check the validity dates at every level.
  4. Check revocation status, usually through CRL or OCSP, although lifetimes are shortening precisely because this step is unreliable.
  5. Confirm the requested name matches a SAN entry, and that the extended key usage permits the purpose.

Failures here are expensive. An expired certificate inside Ericsson software took O2’s UK data network offline on 6 December 2018, affecting around 32 million customers. Microsoft Teams was unavailable for several hours in February 2020 for the same reason. Neither was an attack.

Validation Levels and What They Prove

Domain Validated certificates prove only control of the name, and are issued automatically in seconds. Organisation Validated and Extended Validation certificates add checks on the legal entity. Since browsers removed the EV address bar indicator in 2019, the practical security difference for a visitor is minimal—attackers obtain DV certificates for lookalike domains freely, which is why a padlock proves encryption rather than honesty. The value of OV and EV now lies in internal policy and in some regulated contexts.

Managing Them at Scale

Keep an inventory with owner, issuer, expiry, key algorithm, and renewal method for every certificate, including the internal ones. Monitor Certificate Transparency logs for your domains to spot certificates nobody authorised. Automate issuance through ACME so renewal is not a calendar reminder. Alert on days remaining rather than on job success, and test what happens when a renewal fails. With public lifetimes falling towards 47 days by 2029, manual handling stops being viable—see short-lived certificates for the timetable.

At Privia Security, certificate inventory and chain validation form part of our Continuous Vulnerability Scanning Services, which flag expiring and weakly configured certificates before they fail.

FAQ – Frequently Asked Questions

What Is the Difference Between PEM and DER?

DER is the raw binary encoding of the certificate structure. PEM is that same binary encoded in Base64 and wrapped in BEGIN and END lines, which makes it safe to paste into configuration files and email. They hold identical content, and OpenSSL converts between them in one command. File extensions are inconsistent, so check the first bytes rather than trusting the name.

Why Is the Common Name No Longer Used?

The common name is a single free-text field with no structure, which made it ambiguous and exploitable through null-byte and wildcard tricks. The Subject Alternative Name extension holds a properly typed list of names and supports multiple entries. Browsers have required SAN since 2017 and ignore the common name entirely, so a certificate without SAN simply fails.

Can One Certificate Cover Multiple Domains?

Yes. Listing several entries in the Subject Alternative Name extension produces a multi-domain certificate, and a wildcard entry covers one level of subdomain. The trade-off is blast radius: a single stolen private key then exposes every name on the certificate, and one renewal failure takes them all down together. Split high-value names onto their own certificates.

What Are Name Constraints and Should I Use Them?

Name constraints restrict which domains a certificate authority may issue for, enforced by the verifying client rather than by policy. For a private CA this is valuable: constrain it to your internal namespace so that, even if the CA key is compromised, it cannot produce a trusted certificate for a public bank or email provider. Support is now good across major platforms.

Related Terms

You May Be Interested In These

What Are SPIFFE and SPIRE?

Cybersecurity Terms

17 November 2026

What Are SPIFFE and SPIRE?

Read More
What Is a Cloud Workload Protection Platform?

Cybersecurity Terms

17 November 2026

What Is a Cloud Workload Protection Platform?

Read More
What Are HART and WirelessHART?

Cybersecurity Terms

17 November 2026

What Are HART and WirelessHART?

Read More