Open
Cached
·
just now
93/100
SECURITY SCORE
Certificate Information
Subject
CN=trustcloud.ai
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 13, 2025
Valid Until
March 13, 2026
60 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
5E:CE:A4:B5:30:46:C7:C7:B2:0E:86:88:F5:12:A3:0D:39:62:10:8B:CD:00:B1:DD:BD:4D:1F:E1:6C:6E:FE:C8
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=63072000; includeSubDomains; preload
Content-Security-Policy
Basic
default-src; img-src; media-src; +1 more
default-src * 'self' 'unsafe-inline' 'unsafe-eval' data: blob: strict-dynamic; img-src * data: blob:; media-src * data: blob:; script-src 'self' * 'unsafe-inline' 'unsafe-eval' blob:;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
picture-in-picture=(self *)
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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