Open
Cached
·
just now
95/100
SECURITY SCORE
Certificate Information
Subject
CN=trustedstack.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
September 28, 2025
Valid Until
December 27, 2025
51 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
12:0E:A5:89:C3:F0:AF:7C:87:C9:D8:B3:0D:DE:EC:6B:93:85:BA:56:6D:D6:10:E8:29:96:E2:B1:3B:C4:CC:AD
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
Good
default-src
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
unsafe-url
Permissions-Policy
Present
accelerometer=(*), autoplay=(self), camera=(self), encrypted-media=(self), fullscreen=(self), geolocation=(self), gyroscope=(self), magnetometer=(), midi=(), payment=(), picture-in-picture=(), sync-xhr=(*), usb=(self )
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
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