Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Gravatar
Amplitude
AWS
AWS Certificate Manager
Amazon S3
Bugsnag
ClickCease
Cloudinary
Facebook
Font Awesome
Fullstory
GIPHY
Google Analytics
Google Fonts
Google Optimize
Google Tag Manager
Headway
Hotjar
Segment
Sentry
Smartlook
Stripe
Tapfiliate
Twitter
Unsplash
Vimeo
Wistia
YouTube
Certificate Information
Subject
CN=*.continual.ly
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
February 16, 2026
Valid Until
March 16, 2027
335 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
88:F9:1A:CB:57:B7:C5:E1:70:7F:9F:AC:6F:74:25:18:A9:19:8D:DA:2E:C3:BF:EF:1E:F2:12:5F:14:7A:EF:09
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; includeSubdomains
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
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
- • 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