X.509 Certificate

Why it matters

Encryption alone does not tell you who you are encrypting to. AES-GCM can give you a private channel to a server — but if that server is an attacker's, privacy is worthless. The X.509 certificate is the missing piece: it binds a public key to a domain name and is signed by a Certificate Authority (CA) the browser already trusts, so you get assurance that the key belongs to the real site before any secret is exchanged. That binding is what turns "encrypted" into "encrypted with the right party".

It is also the thing that quietly breaks the web every so often. An expired certificate, a name that does not match, or a broken chain produces the full-page browser warning your users cannot click past. Knowing how to read a certificate is how you tell "genuinely untrustworthy" from "someone forgot to renew".

Fields and the chain of trust

Inside a certificate, a handful of fields do the work:

• Subject — who the certificate is for. Issuer — the CA that signed it. In a self-signed certificate these are the same, which is exactly why browsers do not trust one on its own.
• Subject Alternative Names (SANs) — the actual list of hostnames the certificate is valid for. The old Common Name is effectively ignored now; browsers match against the SANs.
• Validity period (not-before / not-after) — certificates expire deliberately, and public TLS lifetimes keep shrinking.
• Public key and key usage / extended key usage — the key being vouched for and what it may be used for (e.g. server authentication).

Trust is a chain: your server's leaf certificate is signed by an intermediate CA, which is signed by a root CA whose certificate ships pre-trusted in the browser/OS. To get a certificate you first generate a key pair and a CSR (Certificate Signing Request) — a bundle of your identity fields plus your public key, signed by your private key — and the CA turns that into the signed certificate. Your private key never leaves your server.

Common misreadings

• A valid certificate does not mean a safe site. It proves you reached the domain you asked for over an encrypted channel — not that the operator is honest. Phishing sites get free, valid certificates too.
• The Common Name is dead; SANs decide. A certificate can list the right CN and still fail because the hostname is not in the SANs. Always check the SAN list.
• "Chain incomplete" looks like "expired" to users. Forgetting to serve the intermediate certificate breaks trust on many clients even though the leaf is fine — check the whole chain, not just the leaf's dates.

Related terms

• Hash Function — A cryptographic hash function turns any input into a fixed-length digest such that the same input always gives the same output, a tiny change gives a completely different output, and — for a secure one — you cannot work back from the digest to the input or find two inputs that share it.
• AES-GCM — AES-GCM is a symmetric encryption mode that both hides data and detects tampering in one step — it produces ciphertext plus an authentication tag, so decryption fails loudly if even one bit of the ciphertext or its associated data was altered.
• HSTS — HSTS is a response header (Strict-Transport-Security) that tells a browser to only ever reach your site over HTTPS for a set duration, so a later attempt to downgrade the connection to plain HTTP is refused by the browser itself.