Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=niyama.design
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
September 26, 2025
Valid Until
December 25, 2025
38 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
E1:3A:12:1A:F1:76:32:8F:A2:12:6F:F7:F1:08:01:4F:7B:5F:FA:1B:37:4E:91:A8:FD:E9:95:C8:97:8C:4E:0A
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=7889238
Content-Security-Policy
Weak
block-all-mixed-content; frame-ancestors; upgrade-insecure-requests
X-Frame-Options
Excellent
DENY
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
- • Significantly strengthen CSP directives
- • 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