Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=kurviger.de
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 22, 2025
Valid Until
January 20, 2026
40 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
01:14:15:57:0C:C6:25:25:DC:A7:A0:63:D0:FE:23:16:04:07:56:98:BB:6D:6F:14:8E:E9:93:AE:A9:17:8B:EE
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
Good
default-src; object-src; base-uri; +4 more
default-src https: 'self' 'unsafe-inline'; object-src 'none'; base-uri 'none'; frame-src https:; img-src 'self' data: https: blob:; report-uri /web-api/report-to/csp-enforce; font-src 'self' data:;
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Strengthen CSP by removing 'unsafe-eval'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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