Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Google Trust
AWS
Amazon S3
Microsoft Advertising
Cloudflare Turnstile
Cloudflare Web Analytics
Facebook
Google Analytics
Google DoubleClick
Google Fonts
Google Search
Google Tag Manager
Hotjar
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
LinkedIn
Localize.js
Microsoft Clarity
Mixpanel
Active incidents
Segment
Visual Website Optimizer
ZoomInfo
Certificate Information
Subject
CN=quicknode.dev
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 19, 2026
Valid Until
June 17, 2026
42 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
0A:3D:C2:8E:2F:09:41:E7:58:C9:40:E7:F4:49:6A:A4:43:23:45:EA:CD:CB:22:5F:19:74:FC:BD:5F:D2:CA:4F
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
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
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
- • 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