Apple's Certificate Transparency policy

Learn how to comply with Apple's Certificate Transparency policy.

Publicly trusted Transport Layer Security (TLS) server authentication certificates must meet Apple's Certificate Transparency (CT) policy to be evaluated as trusted on Apple platforms.

Certificates that fail to comply with our policy will result in a failed TLS connection, which can break an app’s connection to Internet services or Safari’s ability to seamlessly connect.

Policy requirements

Apple's policy requires at least two Signed Certificate Timestamps (SCT) issued from a CT log — once-approved¹ or currently approved¹ at the time of check — and either:

• At least two SCTs from currently approved CT logs with one SCT presented via TLS extension or OCSP Stapling; or

• At least one embedded SCT from a currently approved log and at least the number of SCTs from once or currently approved logs, based on validity period as detailed in the table below.

At least one SCT must be issued from a log compliant with RFC 6962.

The Number of embedded SCTs required is based on certificate lifetime²:

CT logs

Download the current CT Log list and CT Log list schema in JSON format.