CertH certH

calendly.com SSL Score & TLS Health Report

Issuer
Let's Encrypt
Max TLS
TLS1.2
Cipher
ECDHE-ECDSA-AES128-GCM-SHA256
Expires
12/3/2026( 77 hr)
HSTS
✓ Enabled
OCSP Stapling
Disabled

calendly.com currently holds an SSL grade of A (93/100) from CertH TLS health monitoring. The site supports TLS1.2, has HSTS enabled, and its certificate is issued by Let's Encrypt — certificate validity is unknown. CertH records daily TLS handshake probes into an auditable certificate health trend.

Full certificate & config details

Common Name
calendly.com
Key
ec 256bit
Sig Hash
SHA-384
SAN
*.calendly.com · ablink.e.calendly.com · ablink.send.calendly.com · calendly.com
Fingerprint
e499baafd87cb0767ddd216a2c3a73d6c56888249d8827357a6135c85f0c4dce
Penanda risiko
Tidak ada risiko berarti

Tren skor

02550751009/10/2026, 3:23:57 AM · 93 (A)9/10/2026, 3:24:17 AM · 93 (A)9/18/2026, 3:23:27 AM · 93 (A)9/18/2026, 3:23:47 AM · 93 (A)

Riwayat terbaru

WaktuNilai SkorPenerbit
9/18/2026, 3:23:47 AMA93Let's Encrypt
9/18/2026, 3:23:27 AMA93Let's Encrypt
9/10/2026, 3:24:17 AMA93Let's Encrypt
9/10/2026, 3:23:57 AMA93Let's Encrypt

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).