liveBook · Manning

Certificate

As explained in Real-World Cryptography

A digital certificate is a signed data structure that binds an identity or domain name to a public key.

When a browser connects to google.com, it must distinguish the real server from an impostor. A certificate helps by binding a domain name to a public key through a certificate authority’s signature. section 9.2.1

A browser evaluates a website certificate through a trust chain:

  • The server sends a certificate chain beginning with its leaf certificate, which contains the website’s public key and domain metadata. section 9.2.1
  • Each certificate is signed by the certificate above it; the chain ends at a root certificate already trusted in the browser or operating system trust store. section 9.2.1
  • A certificate authority issues the certificate after the website owner proves control of the domain, such as by hosting a requested file. section 9.2.1
  • Trust can still fail if a certificate authority misbehaves; controlled clients may instead use a private PKI or pin a certificate or public key. section 9.3

Inspecting a certificate

A browser’s certificate viewer can show a chain such as GlobalSign root CA → GTS intermediate CA → Google leaf certificate for *.google.com. OpenSSL can display the issuer, validity period, subject, signature algorithm, and public-key information. section 9.2.1

Figure 9.6 The authentication part of a handshake starts with the server sending a certificate chain to the client. The certificate chain starts with the leaf certificate (the certificate containing the website’s public key and additional metadata like the domain name) and ends with a root certificate that is trusted by the browser. Each certificate contains a signature from the certificate above it in the chain.

Trace how the leaf certificate, intermediate certificates, and trusted root form the authentication chain sent during a TLS handshake. section 9.2.1

How Real-World Cryptography covers it

How deep it goes
Explains issuance, trust chains, certificate contents, encodings, inspection, and CA failure risks without implementation-level validation details.
Examples
Uses Google’s certificate chain, Chrome’s Certificate Viewer, OpenSSL output, domain-validation files, and PEM-encoded certificate data.
What it assumes
Assumes public keys and digital signatures, while reintroducing public key infrastructure through website authentication.
What you can do after
Evaluate/understand how browsers authenticate domains and inspect certificate chains, fields, formats, and trust relationships.
How it connects
Connects certificates to TLS handshakes, web PKI, certificate authorities, digital signatures, trust stores, and certificate revocation.

Also explained in

Compare how 15 books explain certificate →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Real-World Cryptography. The section links point to the parts of the book it draws on.