Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Google Trust
AWS CloudFront
Dreamdata
Google Tag Manager
G2
Google reCAPTCHA
HubSpot Forms
HubSpot Feedback & Surveys
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
ClearBit
AMP
Google Static File Front End
Google API JS Client
Twitter
Hotjar
LinkedIn
HubSpot Analytics
unpkg
Google Search
Facebook
Amazon S3
Mouseflow
AddToAny
Cloudflare CDNJS
AWS
N.Rich
HubSpot
Microsoft Clarity
HubSpot Live Chat
jsDelivr
Google Cloud
Certificate Information
Subject
CN=bd38d9ed.sni.cloudflaressl.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 02, 2026
Valid Until
July 01, 2026
59 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
3C:D9:2D:4B:8D:F5:6C:98:99:B7:C9:05:28:94:FD:94:CF:4B:41:6D:B7:5C:C8:6F:FE:5E:E6:1B:B8:A0:92:DE
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=31536000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
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