ctlogs

Changes to the facts recorded here, not a live scan of every vendor update. Save this tool to follow updates in your account.

1. 9/13/2026

   Updated: best for, export formats, features, integrations, limitations, platforms, sources, summary, use cases, walkthrough

   See recorded changes

   bestFor

   Before: ["Security teams and researchers needing to monitor and investigate TLS/SSL certificates for domains and hosts."]

   After: ["Security teams and researchers needing to verify certificate issuance and detect impersonation or shadow IT."]

   exportFormats

   Before: ["Export selected certificate records as CSV files."]

   After: ["CSV export of selected certificate records is available in paid plans."]

   features

   Before: ["Provides a public API with authentication, rate limits, and endpoints for certificate queries, stats, and account info."]

   After: ["Fast hostname search returning certificates in milliseconds.","Certificate history showing every certificate logged for a name since 2018, including issuer, validity window, type, fingerprint, and other names carried.","Fingerprint lookup by SHA-256 fingerprint to retrieve certificate record details."]

   integrations

   Before: ["MCP connector for AI tools to integrate certificate queries into workflows."]

   After: ["MCP connector for AI tools to access certificate data."]

   limitations

   Before: ["Searches focus on currently valid certificates by default; historical and expired certificates are retained but not shown by default.","The service does not provide subdomain or keyword searches; those are offered by a separate service called DomainKits."]

   After: ["Searches focus on currently valid certificates as default; historical and expired certificates are retained but not shown by default.","The service does not provide subdomain or keyword searches; those are available in a separate service called DomainKits."]

   platforms

   Before: ["Web-based search interface and REST API accessible over HTTPS."]

   After: []

   sources

   Before: [{"url":"https://ctlogs.io/","label":"Certificate Transparency Search | CTlogs.io"},{"url":"https://ctlogs.io/pricing","label":"Pricing | CTlogs.io"},{"url":"https://ctlogs.io/docs","label":"API Documentation | CTlogs.io"}]

   After: [{"url":"https://ctlogs.io/","label":"Certificate Transparency Search | CTlogs.io"},{"url":"https://ctlogs.io/pricing","label":"Pricing | CTlogs.io"},{"url":"https://ctlogs.io/faq","label":"FAQ | CTlogs.io"}]

   summary

   Before: "CTlogs.io is a web service and API platform that indexes public Certificate Transparency logs to allow users to search TLS/SSL certificate records by exact hostname or SHA-256 fingerprint. It provides fast, structured queries over billions of certificate records, showing certificate issuers, validity, and live checks of certificates served by hosts."

   After: "CTlogs.io is a web service that indexes public Certificate Transparency logs, allowing users to search for TLS/SSL certificates by exact hostname or SHA-256 fingerprint. It provides fast, structured searches over certificate records and live checks of what a host currently serves, with data sourced from major CT logs run by Google, Sectigo, and DigiCert."

   useCases

   Before: ["Security teams use CTlogs to detect which certificates exist for a hostname, identify issuing authorities, and verify if a certificate seen in the wild matches the logged record.","Detect misissued or fraudulent certificates quickly by auditing public Certificate Transparency logs."]

   After: ["Security teams use CT data to identify which certificates exist for a hostname, who issued them, and verify if a certificate seen in the wild matches the record."]

   walkthrough

   Before: []

   After: ["Use live check to connect to a host and see the certificate it currently presents, marked in the logged history."]