Open
Cached
·
just now
83/100
SECURITY SCORE
Certificate Information
Subject
CN=validaide.com
Issuer
C=US, O=Google Trust Services, CN=WR1
Valid From
December 12, 2025
Valid Until
March 12, 2026
49 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
37:86:B9:A1:BA:EE:8A:93:26:AC:FF:60:FE:FB:F5:FF:4B:45:6F:8A:B2:0A:6E:3F:D1:AF:07:C0:E0:C7:FF:3F
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=86400
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
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
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
sectigo.com
digicert.com
; cansignhttpexchanges=yes
pki.goog
; cansignhttpexchanges=yes
letsencrypt.org
Wildcard CAs
pki.goog
; cansignhttpexchanges=yes
digicert.com
; cansignhttpexchanges=yes
sectigo.com
letsencrypt.org
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 4 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts