- Issuer
- Sectigo Public Server Authentication CA DV R36
- Max TLS
- TLS1.2
- Cipher
- ECDHE-RSA-CHACHA20-POLY1305
- Expires
- 11/10/2026（ 54 d）
- HSTS
- Disabled
- OCSP Stapling
- Disabled
gitlab.com currently holds an SSL grade of A (93/100) from CertH TLS health monitoring. The site supports TLS1.2, does not enable HSTS, and its certificate is issued by Sectigo Public Server Authentication CA DV R36 — certificate validity is unknown. CertH records daily TLS handshake probes into an auditable certificate health trend.
Full certificate & config details
- Common Name
- gitlab.com
- Key
- rsaencryption 2048bit
- Sig Hash
- SHA-256
- SAN
- gitlab.com · auth.gitlab.com · customers.gitlab.com · email.customers.gitlab.com · gprd.gitlab.com · www.gitlab.com
- Fingerprint
- 8e94ad62fd3380a4f65c17c094a801afbf4dd5f1a6dd29c5f7a8af604cce2d94
Tendência da pontuação
Histórico recente
| Hora | Nota | Pontuação | Emissor |
|---|---|---|---|
| 9/18/2026, 3:23:55 AM | A | 93 | Sectigo Public Server Authentication CA DV R36 |
| 9/18/2026, 3:23:27 AM | A | 93 | Sectigo Public Server Authentication CA DV R36 |
| 9/10/2026, 3:24:17 AM | A | 93 | Sectigo Public Server Authentication CA DV R36 |
| 9/10/2026, 3:23:57 AM | A | 93 | Sectigo Public Server Authentication CA DV R36 |
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).