>_
smartdevbox
Try SmartDevBox free — no sign-up91+ tools · 100% client-side · no account required
Glossary

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

SubjectThe entity the certificate belongs to. For TLS: Common Name (CN) = domain name; Organisation (O), Country (C) for EV certificates.
IssuerThe CA that signed this certificate. For self-signed certs, Issuer == Subject.
ValidityNot Before and Not After dates — the window during which the certificate is valid. TLS certificates now max out at 398 days.
Public KeyThe algorithm (RSA 2048-bit, ECDSA P-256, etc.) and the public key value. Corresponds to the private key held by the certificate owner.
Serial NumberA unique integer assigned by the CA. Used in Certificate Revocation Lists (CRLs) to identify revoked certificates.
Signature AlgorithmThe hash + encryption algorithm used by the CA to sign this certificate. Modern certs use SHA-256 with RSA or ECDSA.
ExtensionsOptional fields defined in RFC 5280. Key ones: Subject Alternative Name (SAN — additional hostnames/IPs), Key Usage, Extended Key Usage (TLS server auth, code signing), Basic Constraints (is this a CA?).

The Chain of Trust

TLS certificates form a chain, not a single link:

  1. 1Root CA — A self-signed certificate pre-installed in your OS/browser trust store. DigiCert, Let's Encrypt ISRG Root X1, etc.
  2. 2Intermediate CA — Signed by the root CA, kept online to issue end-entity certs. Isolates the root from daily operations.
  3. 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

PEMBase64-encoded DER with -----BEGIN CERTIFICATE----- header. Plain text; easy to copy/paste. Most common format for sharing certs on Linux/macOS.
DERBinary ASN.1 encoding of the certificate. Compact; used by Java KeyStore and Windows CertMgr internally.
PFX / PKCS#12Binary bundle containing the certificate, intermediate chain, and private key — password-protected. Common for IIS, Windows, Java key import/export.

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.

Certificate DecoderAuto-detects PEM certificates and displays all fields.
What Is a Hash Function?Certificate signatures use SHA-256 or SHA-384 hashing.
What Is Base64?PEM is a Base64 encoding of the DER binary certificate.