Certificate Transparency Monitor
Introduction
Certificate Transparency is a system for monitoring and auditing publicly-trusted SSL certificates. This website monitors Certificate Transparency log servers to check that they are behaving correctly.
Logs
The list of logs is also available in JSON format at
/logs.json. The schema is identical to the schema
used by the
official
log_list.json and all_logs_list.json files, with
the following exceptions:
- Log operator information is excluded.
- The
final_sth,disqualified_atanddns_api_endpointkeys are excluded. - Keys are
nullif they are not known. - URLs are prefixed with
https://. - A
log_idfield is added, which contains the Base64 hash of the log's key ornullif the key is not known.
Monitors
Gossip is exchanged with the following monitors:
| Monitor | URL |
|---|---|
| Cert Spotter | https://certspotter.com |
| Chromium STHSets | https://clients2.google.com/service/update2/crx |
| ct.x509.io | https://ct.x509.io |
Signed Tree Head gossip
Two API endpoints are provided for exchanging STH gossip:
- /ct/v1/sth-gossip, which implements draft-linus-trans-gossip-ct-01.
- /.well-known/ct/v1/sth-pollination, which implements draft-ietf-trans-gossip-00.
Both return all the STHs observed over the last hour, so there is little point in querying them more than once every 30 minutes. If you use one of these endpoints, I'd appreciate being able to fetch gossip from your monitor in return. In particular, the /ct/v1/sth-gossip endpoint doesn't support exchanging gossip in both directions. Get in touch with me if you want to organise this.
Tor
This website is also available as a Tor hidden service at ctgpe47oofn4ov5v.onion if you want to exchange gossip while remaining anonymous.
Methodology
I've put up a page describing the methodology used by the monitor. If the monitor displays a warning or bad status for a log, you should read the methodology page before reporting it to the log operator (or even better, get in touch, as the web interface doesn't present all of the available data). In particular, the backend is hosted from a residential Internet connection and network outages may cause false positives.