Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Bing
CARTO
Cloudflare CDNJS
Fastly
Firebase
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Gen App Builder
Google Search
Google Static File Front End
Google Tag Manager
jsDelivr
Mapbox
Microsoft Clarity
OpenStreetMap
Perplexity AI
Pexels
Pravatar
Supabase
Active incidents
unpkg
Unsplash
Google Cloud
Certificate Information
Subject
CN=cruvai.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 04, 2026
Valid Until
July 03, 2026
44 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1D:17:E7:EE:46:D1:A0:22:C7:9E:17:E5:66:F5:12:A0:3F:F0:5E:68:6F:B8:CB:4E:71:B8:EA:33:B1:59:51:16
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
Good
max-age=31536000; includeSubDomains
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
- • Consider adding 'preload' to HSTS for maximum security
- • 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