Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
AWS
Microsoft Advertising
DigitalOcean Spaces
Facebook
Google Analytics
Google DoubleClick
Google Fonts
Google Maps
Google Search
Google Tag Manager
Hotjar
HubSpot
HubSpot Forms
jsDelivr
LinkedIn
Localize.js
Microsoft Clarity
Mixpanel
Oracle Cloud
Segment
Sentry
Stripe
Visual Website Optimizer
ZoomInfo
Certificate Information
Subject
CN=quicknode.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
March 31, 2026
Valid Until
June 29, 2026
55 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
0B:E9:2D:EB:63:69:03:8E:B1:95:04:96:2D:55:2C:4C:2E:BB:70:57:4B:BD:0D:C3:3F:4B:FB:AE:C0:59:78:F8
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
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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