Skip to main content

Security report for heyflow.id

Heyflow · Technology · N/A

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

Security score

66/100

Risk levelMedium

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

Heyflow is a technology company providing a SaaS platform for building interactive forms aimed at increasing signups, sales, traffic, and leads. The company positions itself as a market leader with a focus on ease of use, integration capabilities, and design flexibility. The website demonstrates a solid digital presence with modern JavaScript frameworks, cloud hosting on Google Cloud, and integration with major analytics and marketing tools. Security posture is adequate with a valid SSL certificate and cookie consent mechanisms, but lacks advanced security headers and modern TLS protocols. The absence of explicit security policies and vulnerability disclosures suggests room for improvement in transparency and incident response readiness. Overall, the business shows good technical maturity and marketing sophistication but should enhance security practices to reduce risk and build greater trust.

Scanned

This is an earlier scan of heyflow.id. View the latest report

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

  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
    • 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';…

  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

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

Keep watching heyflow.id

This scan found 20 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
80
Security headers
15
Email security
75
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

Heyflow targets businesses and marketers seeking to optimize conversion rates through interactive forms. Its SaaS business model leverages integrations with popular CRMs and marketing platforms, enabling seamless data flow and analytics. The presence of customer logos and multi-lingual cookie consent indicates a broad and international user base. The company benefits from a strong brand identity and a comprehensive feature set including drag & drop design, conditional logic, and extensive icon libraries. Strategic partnerships and service domains support its operational ecosystem. Growth indicators include a free trial offering and emphasis on ease of use. However, lack of explicit company registration or founding year limits deeper corporate profiling.

Security posture

The website employs standard security measures such as a valid SSL certificate and cookie consent aligned with GDPR requirements. However, the lack of HSTS, modern TLS versions, and restrictive CORS policies exposes potential attack vectors. No security.txt or vulnerability disclosure policy is present, which may hinder responsible vulnerability reporting. The open CORS policy and absence of key security headers reduce the overall security score. Incident response contact is indirectly available via a report abuse link but lacks direct security contact emails. Compliance with GDPR is supported by privacy policy and cookie consent but NIS2 or other frameworks are not evident. The security culture appears moderate but could benefit from enhanced transparency and technical controls.

Recommendations

  1. Enable HSTS with includeSubDomains and preload to enforce HTTPS and prevent downgrade attacks.
  2. Upgrade SSL/TLS configuration to support TLS 1.2 or TLS 1.3 protocols for stronger encryption.
  3. Implement restrictive CORS policies to limit resource sharing to trusted origins only.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  5. Publish a dedicated security policy and vulnerability disclosure page to improve transparency and facilitate responsible reporting.
Technical notes

Notes

The infrastructure is hosted on Google Cloud Platform with front-end served via Google Frontend and DNS managed by Cloudflare. The tech stack includes Express.js backend, modular JavaScript, and integration with Google Tag Manager, Google Analytics 4, and Facebook Pixel for marketing and analytics. Performance is optimized with deferred script loading and preloading of fonts. Mobile optimization is good with responsive design elements. However, accessibility and SEO optimizations are basic and could be enhanced. The absence of JSON-LD structured data limits semantic SEO benefits. Technical debt appears low but security configuration gaps present modernization opportunities to strengthen the platform's resilience and compliance posture.
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

Earlier scans of this domain

  1. 65/100Medium34 findingsView report
Reviews of this site

Share your experience with heyflow.id. 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 heyflow.id.

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.