Cross Domain · specification
Certificate Transparency (RFC 6962, RFC 9162)
RFC 6962 and its v2 successor RFC 9162 define append-only, publicly auditable Merkle-tree logs of issued TLS certificates. The mechanism matters well beyond certificates — inclusion and consistency proofs let anyone verify a log was not rewritten without trusting whoever operates it, which is the property API authorization infrastructure is now borrowing.
Also known as CT, CT Log.
Providers that carry Certificate Transparency 0
No provider in the catalog carries this standard as a tag yet. That is a statement about the catalog's tagging, not about adoption: a provider that implements Certificate Transparency and says so in its APIs.json profile appears here on the next build. Add or correct a listing.
Read from the API Evangelist standards directory. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.