CertH certH

creativecommons.org SSL Score & TLS Health Report

Issuer
Google Trust Services
Max TLS
TLS1.2
Cipher
ECDHE-ECDSA-CHACHA20-POLY1305
Expires
11/29/2026( 73 hr)
HSTS
Disabled
OCSP Stapling
Disabled

creativecommons.org currently holds an SSL grade of A (95/100) from CertH TLS health monitoring. The site supports TLS1.2, does not enable HSTS, and its certificate is issued by Google Trust Services — certificate validity is unknown. CertH records daily TLS handshake probes into an auditable certificate health trend.

Full certificate & config details

Common Name
creativecommons.org
Key
ec 256bit
Sig Hash
SHA-256
SAN
creativecommons.org · *.creativecommons.org
Fingerprint
945898e5a474ee32198c2cf83893c449dc72c8db368702281001cc82c8af6325
Penanda risiko
Tidak ada risiko berarti

Tren skor

02550751009/10/2026, 3:23:57 AM · 95 (A)9/10/2026, 3:24:09 AM · 95 (A)9/18/2026, 3:23:27 AM · 95 (A)9/18/2026, 3:23:39 AM · 95 (A)

Riwayat terbaru

WaktuNilai SkorPenerbit
9/18/2026, 3:23:39 AMA95Google Trust Services
9/18/2026, 3:23:27 AMA95Google Trust Services
9/10/2026, 3:24:09 AMA95Google Trust Services
9/10/2026, 3:23:57 AMA95Google Trust Services

Score change insights · Last 90 days

No score changes recorded yet. Once snapshots accumulate, this section shows why the score moved.

FAQ

Why did my SSL score drop?

Common causes include an expiring certificate, legacy TLS protocols enabled, weak cipher suites negotiated, HSTS removed or server handshake failures. The "Score change insights" section below lists the specific reason for each move.

How often is the score updated?

Watched domains are scanned daily; leaderboard domains get weekly full snapshots. Publicly queried domains append history snapshots under throttling, building an auditable score history.

Does certificate rotation affect the score?

Usually not — normal rotation keeps the score unchanged, unless the new certificate changes key strength, issuing CA or signature algorithm. The insights section flags such events.

How can I improve my SSL score?

Enable TLS 1.3, disable TLS 1.0/1.1, use strong cipher suites (AES-GCM / ChaCha20), deploy HSTS correctly, and keep the certificate valid with sufficient key strength (RSA >= 2048 or ECC >= 256).