How the padlock really works β and why it never means a site is honest.
The padlock is not magic β it is a short conversation between your browser and the website. Tap each step to see what really happens.
Your browser does not trust a random website's word for it. It trusts a chain:
| Field | What it tells you |
|---|---|
| Subject / SAN | The domain names the certificate is valid for. A mismatch = browser warning. |
| Issuer | Which CA issued it (e.g. Let's Encrypt, DigiCert, Sectigo). |
| Validity period | Issue and expiry dates. Modern certs last at most ~398 days; browsers warn on expired certs. |
| Public key | Used during the TLS handshake to agree on a one-time session key. |
| Fingerprint | A hash of the whole certificate β its unique ID. |
Tap each statement to reveal whether it is true or false.
| Type | What is checked | Padlock? |
|---|---|---|
| DV β Domain Validation | Only that the applicant controls the domain. Free and automated (e.g. Let's Encrypt). | Yes |
| OV β Organization Validation | Domain control + the organisation legally exists. | Yes |
| EV β Extended Validation | Domain + organisation, verified to a strict standard. Historically showed the company name in the address bar. | Yes |
All three encrypt equally well. The difference is how much identity checking happened β and none of them check whether the site is honest.
Open any website in a new tab, click its padlock / tune icon, and answer what you see. This teaches the exact habit security professionals use.
Keep a log of websites you inspected: what the certificate showed and your verdict. Records are saved under your local account (or guest space) on this device β create, view, edit and delete them any time.