Skip to main content

Security report for dubble.so

Paperform · Technology · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

59/100

Risk levelMedium

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

Dubble is a technology company specializing in automated documentation tools that capture user workflows and convert them into step-by-step guides, videos, and screenshots. Positioned as a niche SaaS provider, Dubble targets individuals and teams seeking to simplify documentation and onboarding processes. The company operates under the parent company Paperform and offers its services primarily through a Chrome extension and web platform. The website demonstrates a strong brand presence with excellent content quality and user experience, supported by modern web technologies such as React and Next.js. Technical infrastructure leverages Cloudflare for DNS and likely CDN services, with integration of Google Analytics and Tag Manager for marketing and analytics purposes. Security posture is adequate with a valid SSL certificate and DMARC email protection, but lacks advanced security headers, DNSSEC, and HSTS enforcement. Privacy and terms of service policies are present and GDPR compliant, though no cookie consent mechanism was detected. Overall, the company shows a mature digital presence with room for security enhancements and improved transparency around incident response and vulnerability disclosure.

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

7 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
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  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

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

Keep watching dubble.so

This scan found 26 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
67
Security headers
30
Email security
35
DNS health
80
Network security
100
GDPR outside view
43
Average
59

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

Dubble operates in the technology sector focusing on documentation automation, competing with tools like Scribe, Tango, Iorad, and FlowShare. Its business model is SaaS-based with a freemium approach via a Chrome extension. The target market includes knowledge workers, teams, and organizations requiring efficient documentation and onboarding solutions. The company benefits from its affiliation with Paperform, enhancing credibility and resource access. Marketing efforts include affiliate programs and active social media engagement. The product's key differentiators are real-time recording, editing capabilities, and seamless sharing across popular knowledge platforms. Growth indicators include a well-structured website, active roadmap, and API documentation. Strategic partnerships and integrations position Dubble well within the documentation and knowledge management ecosystem.

Security posture

Dubble demonstrates a moderate security maturity level with foundational protections such as a valid SSL certificate and DMARC email policy with reporting. However, the absence of DNSSEC, CAA records, and HSTS reduces DNS and transport layer security robustness. No explicit security policy or incident response information is publicly available, indicating potential gaps in transparency and readiness. The website does not provide a vulnerability disclosure program or security.txt file, limiting external security collaboration. The use of third-party analytics and marketing tools introduces moderate user tracking, which is not accompanied by a cookie consent mechanism, potentially impacting privacy compliance. Overall, while basic security hygiene is observed, enhancements in DNS security, HTTP security headers, and incident response transparency are recommended to elevate the security posture.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS and prevent downgrade attacks.
  2. Implement DNSSEC to protect DNS integrity and prevent spoofing or cache poisoning.
  3. Add comprehensive security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  4. Publish a clear security policy and vulnerability disclosure page to improve transparency and encourage responsible reporting.
  5. Establish and publicize incident response contact channels to enhance preparedness and trust.
Technical notes

Notes

The website is built on a modern React and Next.js framework, leveraging server-side rendering and static asset optimization. Hosting and DNS services are provided by Cloudflare, ensuring reliable DNS resolution and potential CDN benefits. Performance metrics indicate moderate load times with a substantial page size and resource count, suggesting opportunities for optimization. Mobile optimization and SEO are good, supported by responsive design and meta tags including Open Graph and Twitter cards. Analytics and marketing integrations include Google Analytics, Google Tag Manager, and an affiliate program via Rewardful. The absence of a CMS suggests a custom-built solution tailored for the product. Technical risks include missing advanced security configurations and potential performance improvements to enhance user experience and security resilience.
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 dubble.so. 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 dubble.so.

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.