Certificate Transparency logs

Browse the public Certificate Transparency log ecosystem — which logs are online, how many entries they hold, and which logs Good Roots monitors for anomaly-focused CT ingestion.

Read the documentationfor data sources, the monitored flag, and the JSON schema.

CT log status

Search and filter all known CT logs. Rows marked Monitored are included in Good Roots ctlogdaemon ingestion.

Loading log status…

Monitored onlyOnline only

Operator	Log	Type	Bucket	Online	Status	Monitored	API	Entries	Last cert	Velocity	Source

What you can do next

Start free— configure domain watches in the monitoring console
Domain Analysis— sneak peek CT certificates for your apex domain
CT log coverage (docs)

FAQ

What does “monitored” mean?: Monitored logs are included in Good Roots’ ctlogdaemon monitor.json configuration — we ingest and evaluate certificates from those logs for watchlist matches and anomaly detection.
Where does this data come from?: We merge Google’s official CT log list, archive.goodroots.work logs.v3.json, and optional Cloudflare Radar CT data, then probe each log for online status, tree size, and velocity.
How often is it updated?: The underlying pipeline (logs2monitorjson) refreshes on its scheduled run. The “Last updated” timestamp on this page reflects the latest published JSON on cdn.goodroots.work.
Can I use the JSON programmatically?: Yes — see the documentation for the machine-readable log-status.json schema (schemaVersion 1).