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
- You can spot a bad certificate. If a certificate appears for your domain from a company you don't use, something is wrong.
- Attackers read the logs too. Every subdomain you ever got a certificate for (
staging,old-shop) is public. Forgotten ones are where subdomain takeovers start. - Renewals are getting more frequent. Certificates can last at most 200 days from March 2026, 100 days from March 2027 and 47 days from March 2029, so automatic renewal is a must.
What to do
- Look up your domain on a CT search (crt.sh is free) and read the list of names.
- Delete DNS records for subdomains you no longer use.
- Add a CAA record listing only the certificate companies you use.
- 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