Certificate Transparency
Certificate Transparency (RFC 9162) requires CAs to submit issued certificates to publicly auditable append-only logs, making mis-issuance discoverable.
Purpose
It makes every CA-issued certificate publicly auditable, detecting CA mis-issuance and unauthorized issuance to strengthen trust in the PKI.
Mechanism
After issuing a certificate, the CA submits it to a CT log, which returns an SCT (Signed Certificate Timestamp). The server presents the SCT during the TLS handshake; browsers verify the SCT and can audit log consistency.
Use cases
- HTTPS certificate auditing
- CA accountability
- PKI transparency
Related tools
HTTP Status Codes
Reference table of common HTTP status codes (1xx-5xx) with names, categories, and descriptions. Free, private, and 100% client-side. TOOL
URL Parser
Parse a URL into its components: protocol, host, path, query, hash, port, username, and password. Free, private, and 100% client-side. TOOL