Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
AppsFlyer
Cloudflare CDNJS
Active incidents
CoinGecko
Cookiebot
Embedly
Active incidents
Facebook
GitHub
Active incidents
Google Analytics
Google DoubleClick
Google Fonts
Google Search
Google Tag Manager
Greenhouse
Rive
Salesforce Cloud
The Trade Desk
Usercentrics
YouTube
Google Cloud Storage
Certificate Information
Subject
CN=blockchain.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 24, 2026
Valid Until
June 22, 2026
54 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
5E:41:0E:EA:B6:D7:2D:8D:61:7D:48:F0:A0:97:D7:6B:21:FA:54:56:B6:53:46:D5:26:45:76:0B:6F:1A:57:BE
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
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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