Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=*.happyreturns.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
August 24, 2025
Valid Until
September 22, 2026
264 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
92:19:8E:53:C7:A5:F4:A8:30:FC:C3:93:D5:34:9F:2F:5C:CF:21:17:4D:BB:BA:97:A4:96:1A:B3:AE:3D:11:5A
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=15768000; includeSubDomains
Content-Security-Policy
Good
default-src; script-src; style-src; +6 more
default-src 'self'; script-src 'self' 'nonce-vAL+V4DvoxiSPJl1sxbBmQ==' https://www.googletagmanager.com https://*.paystand.co https://checkout.paystand.com https://api.paystand.com https://www.google.com https://www.gstatic.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://*.paystand.co https://checkout.paystand.com; img-src * data: blob:; font-src 'self' data: https://assets-dev.happyreturns.com https://assets.happyreturns.com https://fonts.gstatic.com; connect-src 'self' blob: https://featureassets.org https://prodregistryv2.org https://browser-intake-datadoghq.com https://rum.browser-intake-datadoghq.com https://api.paystand.co https://api.paystand.com https://*.google-analytics.com; frame-src 'self' https://checkout.paystand.co https://checkout.paystand.com https://www.google.com https://www.gstatic.com; frame-ancestors 'self'; report-to csp-endpoint;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • 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