What Is an X.509 Certificate?
An X.509 certificate is a digital document that proves a public key belongs to a named entity — a domain, an organisation, or a person. A trusted Certificate Authority (CA) signs the certificate with its own private key, creating a verifiable chain of trust that underlies every HTTPS connection on the web.
The One-Line Definition
An X.509 certificate is a digitally signed data structure that binds a public key to a subject name, enabling a verifier to trust the key without knowing the subject directly. Defined in RFC 5280.
Certificate Fields
The Chain of Trust
TLS certificates form a chain, not a single link:
- 1Root CA — A self-signed certificate pre-installed in your OS/browser trust store. DigiCert, Let's Encrypt ISRG Root X1, etc.
- 2Intermediate CA — Signed by the root CA, kept online to issue end-entity certs. Isolates the root from daily operations.
- 3End-entity certificate — Your domain's certificate, signed by an intermediate CA. Presented to browsers during TLS handshake.
A browser verifies the chain by checking each certificate's signature against the issuer's public key, all the way up to a trusted root.
PEM vs DER vs PFX
Decode a Certificate Now
Paste a PEM certificate (starting with -----BEGIN CERTIFICATE-----) into SmartDevBox. It is auto-detected and all fields are displayed. Open the Certificate Decoder →
Frequently Asked Questions
What is a Certificate Authority (CA)?
A trusted organisation that issues and signs X.509 certificates. Browsers ship with a list of trusted root CAs. When a CA signs your certificate, browsers trust that your public key belongs to your domain.
What is the difference between DER, PEM, and PFX?
DER is binary. PEM is DER Base64-encoded with -----BEGIN/END----- headers — most common for Linux. PFX/PKCS#12 bundles cert + private key in a password-protected binary — common for Windows.
How do I decode an X.509 certificate online?
Paste a PEM certificate into SmartDevBox. It auto-detects the format and shows subject, issuer, validity, public key, and extensions — all client-side.