Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=edwit.de
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 20, 2025
Valid Until
February 18, 2026
32 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
78:F4:82:0D:EF:61:5C:62:8F:0A:70:7C:84:3B:06:48:9A:B7:0C:18:85:12:C3:E7:95:61:24:38:6F:73:E3:87
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Basic
script-src; frame-src; object-src; +1 more
script-src 'self' 'unsafe-inline' 'unsafe-eval' *.edwit.de *.clickskeks.at *.googletagmanager.com *.youtube.com *.gstatic.com *.googleapis.com *.google-analytics.com cdnjs.cloudflare.com; frame-src 'self' *.youtube.com; object-src 'self'; font-src * data:
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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