Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=webexperiences.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
April 08, 2025
Valid Until
May 07, 2026
97 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0B:C6:87:B0:9A:64:BF:31:72:3C:B8:7C:DF:C4:CF:57:4D:3F:1D:2B:92:96:6C:4B:7A:7E:5C:9F:34:C0:68:A7
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=63072000; includeSubdomains
Content-Security-Policy
Basic
default-src; base-uri; form-action; +4 more
default-src 'self' 'unsafe-inline' 'unsafe-eval' *.bound360.com *.bugsnag.com *.cloudfront.net *.getsmartcontent.com *.google-analytics.com *.googleapis.com *.gravatar.com *.gstatic.com *.split.io *.webexperiences.com;base-uri 'self';form-action 'self' *.zendesk.com *.eloqua.com;media-src *;object-src * 'unsafe-eval';img-src * data:;worker-src blob:
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
midi=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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
Subject Alternative Names
6 domains
bound360.com
*.bound360.com
getsmartcontent.com
*.getsmartcontent.com
webexperiences.com
*.webexperiences.com
Other domains in certificate