Open
Cached
·
just now
78/100
SECURITY SCORE
Certificate Information
Subject
C=FR, L=VILLENEUVE D'ASCQ, O=CERTIGNA, CN=ares.certigna.fr, UNKNOWN=S82389790
Issuer
C=FR, O=Certigna, UNKNOWN={:asn1_OPENTYPE, <<12, 20, 78, 84, 82, 70, 82, 45, 52, 56, 49, 52, 54, 51, 48, 56, 49, 48, 48, 48, 51, 54>>}, CN=Certigna Server Authentication OVCP CA G1
Valid From
October 21, 2025
Valid Until
January 19, 2026
52 days
Public Key
RSA
3072 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
CB:C0:DC:B6:4D:D1:8B:5D:85:C0:D5:1B:8C:76:D6:57:F8:3E:75:71:F0:44:EA:DD:BC:7F:4A:89:0E:95:AA:D4
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Content-Type-Options: nosniff
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
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