Open
Cached
·
just now
95/100
SECURITY SCORE
Detected Technologies
Google Trust
Adobe Marketo
Amazon S3
Contentful
Demandbase
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
G Workspace
HubSpot
HubSpot Analytics
HubSpot Forms
LinkedIn
Liveramp
OneTrust
Twitter
YouTube
ZoomInfo
Google Cloud
Certificate Information
Subject
CN=bitgo.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 23, 2026
Valid Until
July 22, 2026
82 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
60:37:20:16:A8:EA:81:FE:08:49:EF:CD:C0:D5:B2:75:AC:E5:E1:5F:65:26:5A:F1:69:C1:12:B7:49:36:78:79
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
accelerometer=(), camera=(), geolocation=(); +5 more
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
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