Open
Cached
·
just now
79/100
SECURITY SCORE
Certificate Information
Subject
C=BG, ST=Bulgaria, L=Sofia, O=SiteGround, OU=Operations Dept., CN=example.com
Issuer
C=BG, ST=Bulgaria, L=Sofia, O=SiteGround, OU=Operations Dept., CN=example.com
Valid From
August 16, 2018
Valid Until
August 13, 2028
708 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1B:DF:6D:0F:EE:4E:7C:1E:A4:68:D8:B4:65:6B:91:C1:DE:24:FB:21:2A:13:D4:55:8D:29:55:A9:5C:75:6B:F3
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports