Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
AWS
AWS Certificate Manager
Amazon S3
Microsoft Advertising
Calendly
Canny
Crowdin
Facebook
FirstPromoter
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Maps
Google Search
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Feedback & Surveys
HubSpot Forms
HubSpot Live Chat
Intercom
LinkedIn
Microsoft Clarity
Mixpanel
Mouseflow
Sentry
Stripe
YouTube
Certificate Information
Subject
CN=portal.leadinfo.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
April 08, 2026
Valid Until
October 22, 2026
181 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
79:23:F0:B6:E1:BD:1E:71:B9:16:30:14:B3:C7:95:DF:CA:E2:8C:5A:5D:F4:22:B9:35:41:9E:D5:2C:59:C0:EB
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=15552000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
accelerometer=(), microphone=(), autoplay=(self); +4 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
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