Explainer · Asset discovery
What is Certificate Transparency?
Certificate Transparency (CT) is a system of public, append-only logs that record TLS certificates as certificate authorities issue them, so anyone can check what was issued for a domain. Defined in RFC 6962 and revised in RFC 9162, it helps owners catch certificates they did not request. It also makes every hostname in those certificates public.
Why CT matters to defenders and attackers
-
Mis-issuance becomes visible
If a certificate for your domain appears that you did not request, a certificate authority made a mistake or someone obtained it improperly. CT is how you find out.
-
A free inventory for attackers
Searching the logs for your domain lists staging servers, internal tools with public names, old campaign sites and vendor-hosted portals.
-
Visible before launch
Certificates are logged when they are issued, often before a new service goes live. A staging host can be public before it is hardened.
-
Permanent by design
Logs are append-only. A hostname that appeared in a certificate stays public after the server behind it is gone.
How Certificate Transparency works
-
The certificate is logged
When it issues a certificate, the certificate authority submits it, usually as a precertificate, to several independent CT logs.
-
Logs return a promise
Each log replies with a signed certificate timestamp (SCT), a signed commitment to publish the entry.
-
Browsers check the proof
SCTs are embedded in the certificate or delivered during the TLS handshake. Major browsers reject publicly trusted certificates that lack them.
-
Monitors and auditors watch
Monitors read the logs for the domains they care about. Auditors use cryptographic proofs to check that each log stays append-only and consistent.
How to check what CT reveals about you
Searching CT logs is a read-only lookup in public data and sends nothing to the hosts you look up. Follow up only on hosts you own or are authorized to test.
-
Search the logs
Use a public CT search service or a CT monitor to list certificates issued for each domain you own, including its subdomains.
-
Extract the names
Collect the hostnames in each certificate’s subject alternative names, then remove duplicates and wildcards.
-
Compare with your inventory
Flag names you do not recognize, services you thought were retired, and certificates from authorities you do not use.
-
Check what still answers
Resolve the flagged names you own. Retired names that still resolve may be takeover candidates; live staging hosts need production-grade protection.
How to limit what CT exposes and use it to your advantage
You cannot remove entries from CT logs. You can control what you add, and watch what others add in your name:
- Restrict who can issue. Publish CAA records that name the certificate authorities allowed to issue for your domains.
- Monitor your domains. Get an alert when a new certificate names one of your hostnames, and investigate the ones you did not expect.
- Keep internal names out of public certificates. Use a private certificate authority for internal-only services. Wildcard certificates hide individual names, but share one private key across every host they cover.
- Assume every logged name is known. Protect staging and admin hosts with authentication, not with an obscure hostname.
- Act on mis-issuance. If a certificate you did not request appears, ask the issuing authority to revoke it and find out how it was obtained.
How NorthBound uses Certificate Transparency
Certificate transparency is one of the sources our attack surface discovery reads, alongside DNS, passive sources and HTTP probing. Reading the logs is part of passive analysis, the testing mode that sends nothing to your systems. New hostnames under your verified domains join your inventory and are covered within the scope and mode you approved, including checks for subdomain-takeover fingerprints.
Questions about Certificate Transparency
Can we remove our hostnames from CT logs?
No. Logs are append-only by design. You can limit what future certificates reveal, for example by using a private certificate authority for internal services.
Are certificates from a private certificate authority logged?
Generally not. Browsers do not trust a private authority by default, so its certificates do not need to be logged.
Is it safe to search CT logs?
Yes. The logs are public by design, and searching them sends no traffic to the hosts they list. Attackers read them for your domains, so you should too.
Do wildcard certificates solve the problem?
Partly. They keep individual names out of the logs, but the hosts can still be found through DNS and probing, and one compromised key affects every host the certificate covers.
Find it before an attacker does.
Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.
Facts on this page verified 11 November 2026.