Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=*.dash.jitjatjo.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
July 30, 2025
Valid Until
August 28, 2026
214 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
78:20:DD:63:E9:64:6C:B1:CD:D0:09:BD:0A:E6:39:C5:AF:29:86:9F:B0:15:E9:12:23:B2:FD:5D:33:93:79:70
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=15768000; includeSubDomains
Content-Security-Policy
Good
default-src; img-src; script-src; +2 more
default-src *;img-src https: blob: data:;script-src https: 'unsafe-inline';style-src https: 'unsafe-inline';frame-ancestors none;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • 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