Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
HTML Load
Apple ID
AWS CloudFront
Let's Encrypt
Google AdSense
Google Maps
Grok
Pinwheel
Google Sign-In
Google reCAPTCHA
Grabyo
Brave Search
Google Translate
Tenor
Castle
Adyen
Vine
Plaid
Google DoubleClick
Google Analytics
Arkose Labs
GIPHY
Google Static File Front End
Google API JS Client
Socure
Google Fonts
Wistia
Twitter
Stripe
Google Search
Facebook
Amazon S3
AWS
Active incidents
Vimeo
Intercom
YouTube
Sentry
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=dresskeep.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
May 07, 2026
Valid Until
August 05, 2026
68 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
18:22:F8:E9:12:55:B1:35:B7:06:FA:5F:98:13:62:AB:ED:37:35:EB:B3:45:E1:01:9D:EA:22:6B:CC:FA:61:06
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=631138519; includeSubdomains
X-Frame-Options
Excellent
DENY
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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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
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