Skip to main content

Security report for hellosign.com

Dropbox Sign · Technology · N/A

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

74/100

Risk levelMedium

0–100, higher is better. How it is calculated

Dropbox Sign, formerly HelloSign, is a leading electronic signature platform integrated with Dropbox, offering easy-to-use eSignature solutions for businesses and developers. The company provides SaaS-based services including document signing, API integration for embedded signatures, fax services, and multiple platform integrations. Their market position is strong, supported by a large enterprise customer base and consistent branding aligned with Dropbox. The website demonstrates excellent content quality, user experience, and trust indicators such as compliance badges and customer testimonials. Technically, the site is built on Webflow CMS, hosted on AWS CloudFront, and uses modern marketing and analytics tools like Adobe DTM and Marketo. Performance and mobile optimization are excellent, with good accessibility and SEO practices. Security posture is solid with valid SSL and security headers, but lacks modern TLS protocols and DNSSEC, and could improve with HSTS and security.txt publication. Overall, Dropbox Sign presents a mature digital presence with strong business and technical foundations, though some security enhancements are recommended.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

4 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      SSL Certificate Expires Soon

      SSL certificate expires in 21 days

      What to do: Renew SSL certificate before expiration

      • NIS2 21(2)(h)
      • IR 2024/2690 9.2(c): Implementing Regulation (EU) 2024/2690, Annex point 9.2(c): Cryptography
      • NIST SC-17: NIST SP 800-53 Rev. 5 SC-17: Public Key Infrastructure Certificates

Need hands-on remediation? Email guard@offseq.com

Keep watching hellosign.com

This scan found 16 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
70
Security headers
45
Email security
95
DNS health
90
Network security
100
GDPR outside view
43
Average
74

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Dropbox Sign operates in the technology and finance sectors, targeting businesses requiring legally binding electronic signatures and workflow automation. Their business model is subscription-based with tiered pricing for end-users and API consumers. The company benefits from Dropbox's parentage, leveraging brand trust and integration capabilities. Their ecosystem includes strategic partners and related services such as Dropbox Forms and Dropbox Fax. Growth indicators include customer testimonials highlighting efficiency gains and API ease of use. Marketing efforts utilize advanced tracking and consent mechanisms, reflecting a mature approach to customer engagement and compliance. The company maintains a consistent brand and professional website, reinforcing market leadership in eSignature solutions.

Security posture

The security posture of Dropbox Sign is generally strong, with valid SSL certificates and implementation of key security headers like Content Security Policy and X-Frame-Options. However, the absence of modern TLS protocols (TLS 1.2/1.3) and HSTS reduces the overall security effectiveness. DNSSEC is not enabled, and CAA records appear misconfigured, which could expose the domain to certain DNS-based attacks. No explicit security policy or incident response information is published on the site, and no security.txt file was found, limiting transparency for vulnerability reporting. Compliance badges such as HIPAA and ISO 9001 indicate adherence to industry standards, but GDPR compliance is inferred rather than explicitly detailed. Incident response readiness and data protection officer contact details are not publicly available, suggesting areas for improvement in security governance and communication.

Recommendations

  1. Enable TLS 1.2 and TLS 1.3 protocols to enhance SSL security and compatibility.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Enable and properly configure DNSSEC to protect DNS integrity and prevent spoofing.
  4. Correct and complete CAA DNS records to restrict certificate issuance to authorized CAs.
  5. Publish a security.txt file and a clear security policy page to facilitate vulnerability disclosure and incident reporting.
Technical notes

Notes

The website is built using Webflow CMS and hosted on AWS CloudFront, ensuring scalability and performance. The tech stack includes jQuery 3.5.1, Adobe DTM for tag management, Marketo for marketing automation, and custom JavaScript for enhanced user experience and tracking. The site is optimized for mobile devices with responsive design and accessibility features such as keyboard navigable accordions. Performance is fast with effective caching and CDN usage. SEO is well implemented with meta tags, Open Graph, and JSON-LD structured data. However, the SSL configuration lacks modern TLS support, and DNS security features like DNSSEC are missing. The site uses multiple external domains for analytics, marketing, and integrations, which are well managed but require ongoing monitoring for security and privacy compliance.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with hellosign.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review hellosign.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.