Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Google AdSense
Google Maps
Criteo
Google Tag Manager
Google Sign-In
Amazon Advertising
Samplicio
Google Translate
OpenX
hCaptcha
Liveramp
Trustpilot
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Datadog
Typeform
Google Static File Front End
DoubleVerify
LaunchDarkly
Google API JS Client
Google Fonts
Hotjar
Zendesk
Stripe
Google Search
Facebook
OneTrust
Pinterest
AWS
AWS Certificate Manager
The Trade Desk
Microsoft Clarity
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=wetransfer.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
March 08, 2026
Valid Until
September 21, 2026
140 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
85:7D:53:ED:73:6F:31:13:BA:D1:AC:2B:89:B6:2D:59:08:FE:D3:6D:42:80:A5:2F:29:EF:18:AD:FF:53:E1:B3
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
Excellent
max-age=31536000; includeSubDomains; preload
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
- • 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