networkutils.org

Home / Security Tools / CT Log Search

CT Log Search

Security Tools

Certificates issued for a domain over time.

Run this tool: the interactive CT Log Search loads here (requires JavaScript). Input: Domain — e.g. example.org.

Description

CT Log Search queries the public Certificate Transparency logs for every TLS certificate issued for a domain over time, revealing every name a CA has validated for the domain — including wildcard and subdomain certificates.

Features

✓ All certificates logged for a domain via crt.sh
✓ Issuer CA and issuance date for each certificate
✓ Wildcard and SAN coverage per certificate
✓ Historical issuance timeline

How to Use

Enter a domain name (example.org) and run the tool. The probe queries the crt.sh Certificate Transparency log search for every matching certificate.

Input: Domain — e.g. example.org.

Understanding the Results

The output lists each certificate with its issuer, the names it covers (SANs), and the issuance date. Unexpected certificates — issued by a CA you do not use, or for a subdomain you did not request — can indicate a mis-issuance or compromise and should be investigated and revoked.

Common Use Cases & Examples

→ Detect unauthorised or mis-issued certificates for your domain.

→ Audit which CAs have issued certificates for your domain.

→ Track certificate issuance history over time.

→ Find wildcard or subdomain certificates you did not know about.

Frequently Asked Questions

What is Certificate Transparency and why does it matter?

CT is a public, append-only log of every TLS certificate a CA issues. It makes mis-issuance detectable: if a CA issues a certificate for your domain without your authorisation, it appears in the log and you can catch and revoke it.

I see a certificate I did not request — what should I do?

Investigate immediately. Confirm whether a teammate or automation requested it. If it is unauthorised, contact the issuing CA to revoke it and report mis-issuance, then review your domain validation and account access for compromise.

Why are there wildcard certificates for my domain?

Someone with control of your domain (or a CA that validated it) requested a wildcard. If you did not, treat it as a potential mis-issuance. Wildcards cover all subdomains, so an unauthorised one is high-risk.

About this tool

Maintained by
networkutils.org editorial team
Last updated
September 2026
Testing methodology
TLS checks perform a real TLS handshake with Node.js tls against port 443 and inspect the presented certificate chain; the Security Headers and Exposure Check tools issue HTTP requests from the server; Subdomain Discovery and CT Log Search query the public crt.sh Certificate Transparency service.
Technical references
RFC 6962 — Certificate Transparency · RFC 9162 — Certificate Transparency 2.0