Open
Cached
·
just now
83/100
SECURITY SCORE
Certificate Information
Subject
CN=www.trinityrocks.com
Issuer
C=US, O=Certainly, CN=Certainly Intermediate R1
Valid From
December 27, 2025
Valid Until
January 26, 2026
25 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
61:2F:19:88:F2:6C:15:D5:41:62:80:9D:B3:32:43:60:2C:FB:24:CA:23:45:91:C1:F3:CD:BF:5A:F1:A5:08:7A
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=31536000
Content-Security-Policy
Weak
upgrade-insecure-requests; base-uri; frame-ancestors
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
bluetooth=(), browsing-topics=(self), camera=(), document-domain=(self), encrypted-media=(), execution-while-not-rendered=(self), execution-while-out-of-viewport=(self), identity-credentials-get=(), picture-in-picture=(self), storage-access=(self)
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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