Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=1millionpixels.dk
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
December 17, 2025
Valid Until
March 17, 2026
75 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
02:65:03:31:AE:33:96:20:30:18:DF:A3:B8:86:2C:44:FB:C0:2E:20:F3:6B:58:D6:A8:21:D1:D5:10:14:2D:E9
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=31536000; includeSubDomains; preload
Content-Security-Policy
Basic
default-src; script-src; connect-src; +3 more
default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://pagead2.googlesyndication.com https://dawa.aws.dk; connect-src 'self' https://pagead2.googlesyndication.com https://api.dataforsyningen.dk https://dawa.aws.dk; img-src 'self' data: blob: https://*; style-src 'self' 'unsafe-inline' https://dawa.aws.dk; frame-src 'self' https://pagead2.googlesyndication.com;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • 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