Skip to main content

Security report for helloworks.com

Dropbox Sign · Technology · N/A

Medium risk. 6 critical or high findings in Email security, Security headers and 2 other checks.

Security score

66/100

Risk levelMedium

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

Dropbox Sign, formerly known as HelloSign, is a leading provider of electronic signature solutions designed to streamline contract signing and document workflows for businesses and developers. Positioned as a scalable and easy-to-use SaaS platform, it offers legally binding eSignatures, API integrations, and additional services such as fax. The company benefits from strong brand recognition as part of Dropbox and serves a broad enterprise audience with a comprehensive suite of features and integrations. Technically, the website is built on Webflow CMS, hosted on AWS CloudFront, and leverages modern marketing and analytics tools like Adobe DTM and Marketo. The site is well-optimized for performance, mobile, accessibility, and SEO, reflecting a mature digital presence. Security-wise, the site employs essential headers and valid SSL certificates but lacks modern TLS protocol support and DNS security extensions, indicating room for improvement. Overall, Dropbox Sign demonstrates a robust business and technical foundation with a strong market position in the eSignature industry.

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

6 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

  2. 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

  3. 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

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

Keep watching helloworks.com

This scan found 19 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
55
DNS health
85
Network security
100
GDPR outside view
43
Average
66

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 sector with a focus on electronic signature and document management solutions. Its business model revolves around SaaS subscriptions and API usage fees, targeting businesses requiring efficient contract workflows and developers embedding eSignatures into applications. The company leverages strategic partnerships and integrations with platforms like Salesforce, Google Drive, and Slack to enhance its ecosystem. Customer testimonials highlight significant efficiency gains and ease of implementation, reinforcing competitive advantages. The parent company Dropbox provides additional market strength and resources. The company emphasizes compliance and trust through certifications and legal binding assurances, catering to regulated industries such as finance and real estate. Growth indicators include extensive customer adoption and a broad resource library supporting user education.

Security posture

The security posture of Dropbox Sign's website is moderate with key strengths including the use of content security policies, X-Frame-Options headers, and absence of known SSL vulnerabilities such as Heartbleed or POODLE. The SSL certificate is valid but uses an unknown algorithm and lacks support for modern TLS versions, which could expose users to downgrade attacks or weaker encryption. DNSSEC and CAA records are not implemented, reducing domain-level security controls. No explicit security policy or incident response information is published on the site, and no security.txt file is found, which limits transparency for vulnerability reporting. Compliance badges such as HIPAA and ISO 9001 indicate adherence to industry standards, but the lack of published security frameworks or DPO contact details suggests potential gaps in formal security governance and incident management readiness.

Recommendations

  1. Enable TLS 1.2 and TLS 1.3 protocols to improve encryption security.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Deploy DNSSEC and CAA DNS records to enhance domain security and certificate issuance control.
  4. Publish a security.txt file to facilitate responsible vulnerability disclosure.
  5. Provide clear security policy documentation and incident response contact information to improve transparency and trust.
Technical notes

Notes

The website is built using Webflow CMS and hosted on AWS CloudFront, ensuring scalable and performant delivery. The tech stack includes jQuery, Adobe DTM for tag management, Marketo for marketing automation, and custom JavaScript for enhanced user experience. The site is optimized for mobile and accessibility, with good SEO practices including hreflang tags for internationalization. Performance metrics indicate fast load times, although no explicit resource counts or page size data were available. The use of multiple external domains for content delivery and integrations is well managed. However, the SSL configuration is outdated, lacking modern TLS support, which poses a technical risk. The absence of DNSSEC and CAA records also indicates technical debt in domain security management. Overall, the technical infrastructure is modern and robust but requires updates in security protocols to align with best practices.
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 helloworks.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 helloworks.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.