Open
Cached
·
just now
78/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Tag Manager
Brightcove
Formulayt
Google Cloud Run
Sift
Iterable
AppNexus (Xandr)
Guideflow
Fullstory
Google Translate
Netlify
Reddit
Webflow
Midbound Cloud
Yahoo
Forter
Liveramp
DocuSign
DigiCert
Google DoubleClick
Google Analytics
Microsoft Advertising
Arkose Labs
Knotch
Mixpanel
Google Cloud Storage
Google Static File Front End
Yellow.ai
Google Fonts
Twitter
Qualtrics
LinkedIn
Contentful
Inbenta
Influ2
Drift
unpkg
Google Search
Demandbase
Facebook
Amazon S3
Sierra
StackAdapt
OneTrust
Adobe Fonts (Typekit)
Cloudflare CDNJS
AWS
Oracle Eloqua
Taboola
SimplyCodes
TechTarget
Akamai
Active incidents
Cloudflare Images
YouTube
The Trade Desk
Optimizely
Sentry
jsDelivr
Google Cloud
Certificate Information
Subject
C=US, ST=California, L=San Francisco, O=DocuSign, Inc., CN=*.docusign.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
January 14, 2026
Valid Until
February 02, 2027
275 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A9:D8:C6:B5:09:D9:E9:17:22:F8:6A:94:F6:A5:DA:17:26:11:2B:0E:5B:19:25:DD:06:A5:C7:4F:53:0E:A6:6C
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=31536000
Content-Security-Policy-Report-Only
Basic
default-src; script-src; script-src-elem; +11 more
Analyze
X-Frame-Options
Missing
Not configured
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
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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
Subject Alternative Names
31 domains
*.docusign.com
au.act-apps.docusign.com
au.act-archive.docusign.com
au.act-event.docusign.com
au.act-opslog.docusign.com
au.act-rules.docusign.com
au.act-store.docusign.com
ca.act-apps.docusign.com
ca.act-archive.docusign.com
ca.act-event.docusign.com
ca.act-opslog.docusign.com
ca.act-rules.docusign.com
ca.act-store.docusign.com
eu.act-apps.docusign.com
eu.act-archive.docusign.com
eu.act-event.docusign.com
eu.act-opslog.docusign.com
eu.act-rules.docusign.com
eu.act-store.docusign.com
jp.act-apps.docusign.com
jp.act-archive.docusign.com
jp.act-event.docusign.com
jp.act-opslog.docusign.com
jp.act-rules.docusign.com
jp.act-store.docusign.com
na.act-apps.docusign.com
na.act-archive.docusign.com
na.act-event.docusign.com
na.act-opslog.docusign.com
na.act-rules.docusign.com
na.act-store.docusign.com