Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
C=FR, L=PARIS, O=VILLE DE PARIS, CN=*.paris.fr, UNKNOWN=S3675100234
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
December 17, 2025
Valid Until
March 16, 2026
81 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
CA:A0:E2:3F:2E:45:6B:E3:74:12:39:25:DB:B0:1B:37:AC:C3:08:90:74:49:80:C0:CE:B1:F4:9D:42:CC:C7:22
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=31557600
Content-Security-Policy
Weak
img-src; frame-ancestors; frame-src
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • 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