The padlock is a lie until you read the cert

Before you start

An auditor asks one two-part question — "is the data encrypted at rest AND in transit?" — and a green padlock is offered as the answer. It is not the answer. You are handed real cryptographic artifacts and asked to read each half's truth directly off the bytes: sort hash from encrypt from encode by running the real transform, peel the real www.google.com certificate to the one field that anchors the in-transit claim, assemble the TLS 1.3 handshake until the sim refuses an illegal move with the real RFC 8446 alert, and click the single field that breaks each broken cert. Every value you reveal is the real parser / state-machine / transform over the real artifact — the same fields `openssl x509 -text` prints, the same return codes `openssl verify` emits (0/10/18/62), and SHA-256("") = e3b0c442… recomputed live. Nothing is invented; the transform is the answer key. Start on the "Sort · SHA-256" card.