The problem
Asymmetric encryption is great, but how do you know a public key really belongs to yourbank.com and not an attacker? You need someone trusted to vouch for it.
Digital signatures
- Hash the message
- Encrypt the hash with your private key: that’s the signature
- The receiver checks it using your public key
A valid signature proves three things:
- Authenticity: it came from the private key’s owner
- Integrity: it hasn’t been changed
- Non-repudiation: the signer can’t credibly deny signing it
Certificates
A digital certificate (X.509) is like an ID card for a public key. It contains:
- The subject (e.g.
dash8.binjesoft.online) - The subject’s public key
- The issuer (which CA signed it)
- Validity dates
- The CA’s signature
The chain of trust (PKI)
Root CA (pre-installed in your OS/browser, kept offline)
└─ Intermediate CA (does day-to-day signing)
└─ dash8.binjesoft.online (the site's certificate)
Your browser follows the chain up to a root CA it already trusts. If any link is broken, expired or untrusted, you get a scary warning. Don’t click through it on sites that matter.
When things go wrong
- Expired certificate: renew it (automation like ACME / Let’s Encrypt helps)
- Private key stolen: revoke the certificate. Clients check revocation via a CRL (revocation list) or OCSP (online check).
- Self-signed certificates aren’t vouched for by anyone. They’re fine for testing, not for public sites.
Remember: the padlock proves you’re talking to the domain in the address bar. It doesn’t prove that domain is honest. Phishing sites have valid certificates too!