82/100 SECURITY SCORE

Certificate Information

Subject
CN=*.wikipedia.org
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
February 06, 2026
Valid Until
May 07, 2026 29 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
34:61:AA:F3:0B:87:E6:FF:B7:49:69:AE:7A:96:EF:A4:E8:E1:C6:A2:A3:9A:21:3E:D3:AB:D5:D1:7D:E9:27:9F
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
Excellent
max-age=106384710; includeSubDomains; preload
Content-Security-Policy
Basic
default-src; object-src; report-uri Analyze
Content-Security-Policy-Report-Only
Basic
script-src; default-src; style-src; +2 more Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • 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