Open
Cached
·
just now
87/100
SECURITY SCORE
Detected Technologies
PayPal
HTML Load
Google AdSense
Google Maps
Google Tag Manager
Bing
Google reCAPTCHA
Sift
Braintree
Sardine
AppsFlyer
Fullstory
Reddit
Plaid
Google DoubleClick
Google Analytics
Google Conversion Tracking
Google Static File Front End
Google API JS Client
Socure
TikTok Analytics
Google Fonts
Twitter
LinkedIn
Zendesk
Google Search
Facebook
Snapchat
Entrust Identity Verification
AWS Certificate Manager
MNTN
Microsoft Clarity
Sentry
Google Cloud
Certificate Information
Subject
CN=exchange.gemini.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
March 24, 2026
Valid Until
October 07, 2026
164 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
95:7C:D2:DC:71:18:E8:7F:87:15:18:63:FC:A9:6E:84:34:66:E7:A8:6C:AA:1E:23:C2:F2:C9:FE:4B:7E:F6:74
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=15552000; 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
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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