Your domain, checked and fixed.

Learn DNS · Level 4: Keep your domain safe · lesson 28 of 34 · 2 min

HTTPS certificates and the public log anyone can read

Direct answer: Every HTTPS certificate is written to public logs. You can see every certificate ever issued for your domain, and so can attackers.

The picture: Every HTTPS certificate is written into a public logbook that anyone can read, like a register of every key ever cut for every door.

What the logs are

Since 2018, browsers only trust a certificate if it has been written to public Certificate Transparency logs. The logs can't be edited, so a certificate issued by mistake or by an attacker can't stay secret.

Why it matters to you

What to do

  1. Look up your domain on a CT search (crt.sh is free) and read the list of names.
  2. Delete DNS records for subdomains you no longer use.
  3. Add a CAA record listing only the certificate companies you use.
  4. If you see a certificate you don't recognise, read what to do about an unexpected certificate.

Try it

The free check reads the logs for you and flags forgotten subdomains.

Back to the picture: If a key was cut for your door and you didn't ask for it, the logbook shows it. That's what a certificate alert watches for.

Try it on your domain:

List my certificates and subdomains