Open
Cached
·
just now
87/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
YouTube
Google AdSense
Fern
Pingdom
Google Tag Manager
Ahrefs
Google Cloud Run
CodeSandbox
CookieHub
hCaptcha
Statuspage
Zapier
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Pusher
Google Static File Front End
Google API JS Client
Google Fonts
Algolia
LinkedIn
ZoomInfo
Stripe
unpkg
Google Search
Facebook
Amazon S3
Kapa AI
Maxio
Rollbar
AWS
Salesforce Pardot
AWS Certificate Manager
Visual Website Optimizer
Google Cloud
Certificate Information
Subject
CN=uploadcare.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
February 11, 2026
Valid Until
March 11, 2027
310 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B9:1B:1E:6C:ED:E8:29:25:02:21:77:72:0D:B7:D0:BA:2C:B3:42:BB:5F:D3:71:68:47:E9:39:95:75:27:C8:0C
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
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
ORIGIN
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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