SSL Certificate Analysis for apps.docusign.com - Security Grade & TLS Configuration

Open Cached · just now

86/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 22

Adobe Fonts (Typekit)

Akamai

Arkose Labs

Brightcove

Contentful

DigiCert

DocuSign

Google Analytics

Google API JS Client

Google Fonts

Google Static File Front End

Google Sign-In

G Workspace

Heroku

Microsoft 365

Mixpanel

Optimizely

PubNub

Qualtrics

Salesforce Cloud

YouTube

Google Cloud

Certificate Information

Subject

UNKNOWN={:asn1_OPENTYPE, <<19, 2, 85, 83>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 8, 68, 101, 108, 97, 119, 97, 114, 101>>}, UNKNOWN={:asn1_OPENTYPE, <<12, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, UNKNOWN=5711317, C=US, ST=California, L=San Francisco, O=Docusign, Inc., CN=cdn.docusign.com

Issuer

C=US, O=DigiCert Inc, CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1

Valid From

April 09, 2026

Valid Until

October 06, 2026 149 days

Public Key

ECDSA 256 bit (P-256) Adequate

Signature Algorithm

ECDSA-SHA384

SHA-256 Fingerprint

25:9D:29:CD:C5:A3:9F:0A:BD:FB:74:A8:76:16:F7:E2:27:9A:43:E7:B6:A1:77:73:B0:7D:CF:5B:35:06:9E:7B

Alternative Names

95 domains

Security Configuration

TLS Protocols

TLS 1.2 TLS 1.3

Forward Secrecy

Supported (Modern clients use PFS)

HTTP Security Headers

Status

Strict-Transport-Security

Good

max-age=31536000; includeSubDomains

Content-Security-Policy

Good

default-src; base-uri; block-all-mixed-content; +15 more Analyze

Content-Security-Policy-Report-Only

Good

default-src; base-uri; block-all-mixed-content; +13 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

• Consider adding 'preload' to HSTS for maximum security
• Strengthen CSP by removing 'unsafe-eval'
• 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