Open
Cached
·
just now
77/100
SECURITY SCORE
Certificate Information
Subject
C=FR, L=PARIS, O=VILLE DE PARIS, CN=*.paris.fr, UNKNOWN=S3590807351
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
September 23, 2025
Valid Until
December 21, 2025
30 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E8:9A:F1:32:A8:4D:13:F2:6C:3D:3A:6C:BE:B1:60:7E:B9:3B:F1:72:17:EE:78:40:2A:56:D4:60:B1:74:93:7E
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
Present
max-age=15768000
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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