Open
Cached
·
just now
85/100
SECURITY SCORE
Detected Technologies
Google Trust
PayPal
YouTube
Adyen
Arcade
Arkose Labs
Active incidents
AWS
Brightcove
Cloudinary
DocuSign
Active incidents
Embedly
Active incidents
Google Pay
Google reCAPTCHA
Google Search
Google Static File Front End
Mixpanel
Salesforce Cloud
Salesforce Sites
Stripe
Vidyard
Vimeo
Wistia
Google Cloud
Certificate Information
Subject
CN=dojo.tech
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 24, 2026
Valid Until
July 23, 2026
76 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
44:9F:55:7C:C8:D2:C6:BB:52:39:2E:AB:5B:1C:35:EE:94:92:5D:7F:F6:0E:A2:AD:78:31:05:02:E2:B1:4D:5A
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
Weak
max-age=0
X-Frame-Options
Present
ALLOWALL
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • 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