Certificate Transparency
Also called CT.
Public append-only logs of every issued TLS certificate.
What it is
A system of publicly auditable, append-only logs that record certificates as they are issued. Browsers can require that a certificate appear in these logs to be trusted.
Why it matters
CT makes mis-issued or fraudulent certificates discoverable, letting domain owners and defenders spot unauthorized certificates for their names. Monitoring CT logs is a practical early-warning signal for phishing and impersonation infrastructure.
In practice
A security team finding a lookalike domain's certificate in CT logs days before a phishing campaign launches.
What to look for
- Certificates for lookalike domains appearing in logs.
- Subdomains you did not know existed listed in logs.
- Certificates issued by CAs you never use.
Common mistake
Ignoring the logs because they are public. Attackers read them too, so watch them first.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Nmap Open source
Scans hosts for open ports and services, the same view an attacker gets.
-
Shodan Commercial
A search engine for internet facing devices, useful for seeing what you expose.
-
Nuclei Open source
Runs template based checks for exposures and misconfigurations across many targets.
Tools practitioners use
- crt.sh: Certificate transparency log search
Read next
- Certificate Authority: A trusted entity that issues and signs digital certificates.
- Public Key Infrastructure: The system of authorities and certificates that binds keys to identities.
- Digital Signature: A cryptographic proof of a message's origin and integrity.