Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Criteo
Google Tag Manager
Bing
Google reCAPTCHA
ShareThrough
Google Cloud Run
Amplitude
AppNexus (Xandr)
AppsFlyer
Reddit
Yahoo
Statuspage
HubSpot Forms
HubSpot Feedback & Surveys
Google DoubleClick
Google Analytics
Crazy Egg
Google Conversion Tracking
Adobe Audience Manager
Segment
Datadog
Typeform
Google Cloud Storage
Google Static File Front End
Outbrain
TikTok Analytics
Google Fonts
Twitter
G Workspace
Hotjar
LinkedIn
PubMatic
Zendesk
Contentful
HubSpot Analytics
Teads
Yieldmo
Google Search
Facebook
Matomo
TripleLift
Taboola
Rubicon Project
Visual Website Optimizer
HubSpot
HubSpot Live Chat
Google Cloud
Certificate Information
Subject
CN=api.bitso.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
March 11, 2026
Valid Until
June 09, 2026
33 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
39:23:23:CA:43:5D:BB:05:87:9A:96:20:CC:0F:F3:95:50:CC:27:E3:CC:D3:A7:21:DF:8C:DD:57:40:E6:7C:7F
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
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
microphone=(), usb=()
Recommendations
- • Significantly strengthen CSP directives
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