- Issuer
- Let's Encrypt
- Max TLS
- TLS1.3
- TLS versions
- TLS 1.3 TLS 1.2 TLS 1.1 TLS 1.0
- Cipher
- ECDHE-ECDSA-AES128-GCM-SHA256
- Expires
- 1/11/2027 ( 66 d)
- HSTS
- ✓ Enabled
- OCSP Stapling
- Disabled
- Last scanned
- 11/4/2026, 12:51:19 PM
Report summary
csr.run currently holds an SSL grade of A+ (98/100) from CertH TLS health monitoring. The site supports TLS1.3, TLS1.2, has HSTS enabled, and its certificate is issued by Let's Encrypt — 66 days left on the certificate. CertH records daily TLS handshake probes into an auditable certificate health trend.
Excellent — A near-perfect setup: TLS 1.3, strong ciphers, full forward secrecy (PFS) and correctly enabled HSTS. First choice for finance, payments and other high-stakes businesses.
csr.run scores higher than 99% of the 12,269 sites we grade.
Percentile is computed over the 12,269 sites CertH has indexed (including ungraded ones), not an industry census.
Last scanned 2 days ago — this data may be stale
Full certificate & config details
- Common Name
- csr.run
- Key
- ec 256bit
- Sig Hash
- SHA-384
- Chain
- Complete
- SAN
- csr.run
- Fingerprint
- 7e7c1ad9ac8dbe76aba443d01a9bd98294b323db344f44bada7b087062927bb6
What’s working
- TLS 1.3 enabled
- HSTS enabled with a long max-age
- Complete certificate chain
- No legacy TLS or weak ciphers
Score trend
Recent history
| Time | Grade | Score | Issuer |
|---|---|---|---|
| 11/4/2026, 12:51:19 PM | A+ | 98 | Let's Encrypt |
| 9/10/2026, 10:27:55 AM | A | 93 | Let's Encrypt |
Score change insights · Last 90 days
Net change ↑ +5-
↑
11/4/2026 +5 A → A+CA changedTLS version support improvedAlso observedCAA: — → —
FAQ
When does csr.run’s certificate expire?
csr.run’s certificate expires on 1/11/2027, in 66 days, issued by Let's Encrypt.
Is csr.run’s TLS configuration secure?
csr.run currently scores A+ (98/100). It negotiates TLS1.3, TLS1.2 and has HSTS enabled.
Why did csr.run’s score change?
11/4/2026: +5 points — CA changed · TLS version support improved