Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
Amazon CloudFront
DebugBear
Google Tag Manager
SalesLoft
Google Cloud Run
Amplitude
Braintree
Google Hosted Libraries
Reddit
Google DoubleClick
Google Analytics
Google Conversion Tracking
Google Static File Front End
TikTok Analytics
Google Fonts
Osano
Cloudinary
LiveChat
unpkg
Bootstrap
Google Search
Facebook
Amazon S3
Adobe Fonts (Typekit)
Pinterest
Cloudflare CDNJS
AWS
jQuery
AWS Certificate Manager
YouTube
Font Awesome
jsDelivr
Google Cloud
Certificate Information
Subject
CN=avery.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
September 05, 2025
Valid Until
October 03, 2026
228 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
99:66:A1:44:7B:69:1B:ED:4F:88:C5:50:B1:AB:73:C7:E9:10:04:C2:8D:F3:83:4C:93:77:99:74:A8:E5:DA:1F
Alternative Names
Security Configuration
TLS Protocols
TLS 1.1
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
- • TLS 1.1 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=3600;includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(), camera=(), microphone=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
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