Skip to main content

Security report for howdygo.com

HowdyGo · Technology · N/a

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

Security score

69/100

Risk levelMedium

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

HowdyGo is a SaaS company specializing in interactive product demo software designed for go-to-market teams. Their platform enables users to create embedded product demos and live demo environments that are easy to share and edit. The company targets marketing and sales teams seeking to improve product engagement through interactive demos. The website presents a professional and modern interface with clear messaging and customer trust signals such as case studies and testimonials. Technically, the site is built on modern frameworks including Next.js and React, with integrations for analytics and customer chat support. Security posture is strong with HTTPS and security headers, though explicit privacy and security policies are not published. The domain WHOIS data is not publicly available, likely due to privacy protection, which is common for SaaS businesses. Overall, the site is trustworthy and well-implemented but could improve transparency around privacy and security policies.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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

5 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 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

  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

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching howdygo.com

This scan found 23 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. See sample alerts.

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
72
Security headers
30
Email security
85
DNS health
75
Network security
100
GDPR outside view
53
Average
69

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

HowdyGo occupies a niche in the technology sector providing interactive demo software as a service. Their business model is subscription-based with a free trial to attract users. The company leverages partnerships with CRM platforms and integrates marketing tools such as Google Analytics and LinkedIn Insight. Their competitive advantage lies in offering pixel-perfect HTML demos that can be edited post-recording, differentiating from traditional screen recording tools. The target customers are marketing and sales teams in technology companies. Growth indicators include multiple case studies and customer logos displayed on the site. The company maintains a consistent brand and professional content, supporting a high trust level among visitors.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and multiple security headers present. There is no evidence of exposed sensitive data or vulnerable libraries in the HTML content. However, the absence of published privacy, cookie, security, and incident response policies indicates gaps in compliance and transparency. No vulnerability disclosure program or security.txt file was found, which could limit external security reporting. The site uses third-party analytics and chat services, which may introduce privacy considerations. Overall, the security maturity is good but could be enhanced by publishing comprehensive policies and contact channels for security incidents.

Recommendations

  1. Publish a comprehensive privacy policy and cookie consent mechanism to improve privacy compliance and user trust.
  2. Add explicit security and incident response policies accessible from the website footer or dedicated pages.
  3. Implement and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Provide clear contact information for security incidents, including dedicated security or abuse email addresses.
  5. Regularly review third-party scripts and tracking tools to ensure minimal privacy impact and compliance with regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
HowdyGo
Description
Give hands on access to your product with embedded product demos and stress-free live demo environments.
Key services
Interactive product demos, Embedded product demos, Live demo environments, Demo editing and export, CRM lead sync
Content quality
good
Branding
consistent

Technology

Stack
Next.js, React, Tailwind CSS, Crisp Chat, Google Tag Manager, LinkedIn Insight, HowdyGo SDK
Frameworks
Next.js, React
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of modern JS frameworks
  • No visible vulnerable libraries

Analytics and tracking

Services
Google Analytics, LinkedIn Insight
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
LinkedIn Insight
Marketing tools
HowdyGo SDK, Crisp Chat
Transparency
basic

Site quality

Design
excellent
User experience
excellent
Content relevance
good
Navigation
good
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. No explicit privacy, cookie, or terms of service pages found in the HTML content provided.
  3. No contact emails or phone numbers explicitly found in the visible content or metadata.
  4. Use of modern web technologies and frameworks indicates up-to-date technical implementation.
  5. Strong branding and customer logos provide trust signals.
  6. No security.txt or vulnerability disclosure information found.
  7. No explicit security or incident response policies published on the site.
  8. Tracking and analytics scripts are present but no aggressive tracking detected.
  9. No suspicious or malicious domains linked.
  10. WHOIS data is missing, indicating privacy protection or new domain registration.
Technical notes

Notes

The website is built using modern web technologies including Next.js and React, supported by Tailwind CSS for styling. It integrates third-party services such as Crisp Chat for customer support and Google Tag Manager for analytics. The site is mobile-optimized with responsive design and good accessibility features. Performance appears fast with efficient loading of fonts and scripts. No CMS is detected, indicating a custom or framework-based build. Hosting provider details are not explicitly found. The technical implementation is robust with opportunities to enhance SEO and privacy compliance through additional metadata and policy pages.
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 howdygo.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 howdygo.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.