Skip to main content

Security report for hashgrowth.org

MoEngage Inc. · Technology · N/a

Medium risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

72/100

Risk levelMedium

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

MoEngage Inc. operates a customer engagement platform focused on marketing automation and analytics, serving businesses across multiple industries. The website content analyzed is primarily a 404 error page but includes global header and footer elements linking to MoEngage's main corporate site and services. The technical infrastructure leverages HubSpot CMS, Cloudflare CDN, and integrates Google Analytics and OneTrust for tracking and cookie consent. However, the site suffers from a lack of a valid SSL certificate and multiple SPF records, which negatively impact security posture and email deliverability. Privacy compliance is partially addressed with a privacy policy and cookie consent mechanism, but explicit security and incident response policies are not publicly found. Overall, the site demonstrates moderate business credibility but requires significant improvements in security and technical implementation to enhance trust and compliance.

Scanned

This is an earlier scan of hashgrowth.org. 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

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

  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 hashgrowth.org

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
90
Security headers
55
Email security
70
DNS health
75
Network security
100
GDPR outside view
43
Average
72

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

MoEngage positions itself as a mid-sized technology company specializing in customer engagement solutions including push notifications, email campaigns, and analytics. The business model is SaaS-based, targeting enterprises and businesses seeking marketing automation tools. The presence of Gartner widgets and partnership links indicates a focus on market credibility and ecosystem partnerships. The site content and navigation reflect a professional but basic user experience, with clear branding consistency. The company leverages HubSpot for CMS and marketing automation, indicating a mature digital marketing approach. However, the lack of valid SSL and SPF misconfigurations suggest operational gaps that could affect reputation and deliverability.

Security posture

The security posture is weak due to the absence of a valid SSL certificate and lack of modern TLS protocols, exposing users to potential risks. While some security headers like HSTS and CSP are present, critical gaps remain such as invalid SPF records and missing OCSP stapling. No public security or incident response policies were found, indicating limited transparency and preparedness. The site does not appear to be behind a WAF or security challenge, but the technical security controls require urgent enhancement to meet industry standards and regulatory compliance.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate supporting TLS 1.2 or higher to secure all site traffic.
  2. Consolidate SPF records into a single valid record to ensure proper email authentication and reduce spam risks.
  3. Publish explicit security policies and incident response procedures to improve transparency and compliance.
  4. Enhance mobile optimization and accessibility to improve user experience and SEO.
  5. Enable OCSP stapling and session resumption to improve SSL performance and security.
Technical notes

Notes

The website is built on HubSpot CMS and uses Cloudflare for CDN services. It incorporates legacy jQuery 1.7.1 and modern marketing tools like Google Analytics 4 and OneTrust for cookie consent. Performance is slow with no page size or resource count data available, likely due to the 404 error page content. SEO is basic with meta tags present but minimal content. Accessibility features are limited. The DNS setup uses AWS Route53 nameservers without DNSSEC or CAA records. SPF records are misconfigured with multiple entries causing validation failure. SSL configuration is poor with no valid certificate and no TLS protocols enabled, severely impacting security 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. 75/100Medium28 findingsView report
Reviews of this site

Share your experience with hashgrowth.org. 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 hashgrowth.org.

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.