Open
Cached
·
just now
67/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=California, L=Santa Barbara, O=Apache HTTP Server, OU=For Testing Purposes Only, CN=localhost, UNKNOWN=root@localhost
Issuer
C=US, ST=California, L=Santa Barbara, O=Apache HTTP Server, OU=For Testing Purposes Only, CN=localhost CA, UNKNOWN=root@localhost
Valid From
October 13, 2018
Valid Until
October 12, 2020
Expired
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
3A:95:5B:44:06:7C:1E:53:68:E7:1B:16:32:CC:26:93:56:AE:71:1B:64:AF:45:98:9B:92:E0:BF:B1:CF:D4:12
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