Skip to main content

Security report for hashgrowth.org

MoEngage · Technology · United States

Medium risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

75/100

Risk levelMedium

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

MoEngage is a technology company specializing in customer engagement and marketing automation solutions. The company offers a comprehensive SaaS platform that includes push notifications, email campaigns, in-app messaging, web push, SMS marketing, and customer analytics. Positioned as an enterprise-grade solution, MoEngage targets businesses seeking to enhance customer retention and engagement through data-driven marketing strategies. The website content and branding are consistent with a professional B2B SaaS provider, supported by trust signals such as Gartner Peer Insights ratings and integration with HubSpot marketing tools. Technically, the website is built on HubSpot CMS and leverages a modern technology stack including Google Analytics 4, Facebook Pixel, LinkedIn Insight Tag, and other marketing and analytics tools. Hosting is provided via AWS infrastructure, and the site demonstrates good mobile optimization and moderate performance. Privacy compliance is well addressed with clear privacy and cookie policies and a consent mechanism implemented via OneTrust. From a security perspective, the site enforces HTTPS and uses cookie consent mechanisms but lacks visible advanced security headers and published security policies or incident response contacts. The domain is privacy protected via Domains By Proxy, which is justified for this business type. No WAF or blocking mechanisms were detected, and no vulnerabilities or suspicious patterns were found in the WHOIS or site content. Overall, the website presents a trustworthy and professional front for MoEngage, though the analyzed URL is a 404 error page, limiting content quality. Recommendations include enabling DNSSEC, publishing a security policy, and adding vulnerability disclosure information to enhance security posture and transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
100/ 100 · Low
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. 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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching hashgrowth.org

This scan found 19 issues across 5 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
47
Security headers
55
Email security
70
DNS health
75
Network security
100
GDPR outside view
100
Average
75

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 operates in the competitive customer engagement and marketing automation market, leveraging a SaaS business model focused on enterprise clients. The company differentiates itself through multi-channel messaging capabilities and advanced analytics. Its partnership ecosystem includes recognized entities like Gartner, enhancing credibility. The business model relies on subscription revenues from its platform services. Growth indicators include active marketing, extensive analytics tracking, and a comprehensive content strategy on the main domain. The use of HubSpot and AWS indicates investment in scalable infrastructure. The lack of direct phone contacts on this domain suggests a digital-first customer engagement approach.

Security posture

The security maturity level is moderate. The site uses HTTPS and cookie consent mechanisms, indicating baseline security and privacy awareness. However, the absence of security headers and published security or incident response policies suggests room for improvement. No exposed sensitive data or vulnerable libraries were detected. The domain's privacy protection is appropriate but obscures registrant details. Compliance with GDPR is indicated by the presence of privacy and cookie policies. Incident response readiness and vulnerability disclosure mechanisms are not evident, representing a compliance gap. Overall, the security culture appears focused on marketing compliance rather than advanced security transparency.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a dedicated security policy page outlining security practices and incident response procedures.
  3. Implement and serve security headers such as Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options.
  4. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Enhance accessibility features and SEO metadata to improve user experience and search engine visibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
MoEngage
Description
MoEngage is a customer engagement platform offering marketing automation, analytics, and multi-channel messaging solutions.
Key services
Push Notifications, Email Campaigns, In-app Messaging, Web Push, SMS Marketing, Customer Analytics
Content quality
good
Branding
consistent

Technology

Stack
HubSpot CMS, Google Tag Manager, Google Analytics 4, Facebook Pixel, LinkedIn Insight Tag, Bing Ads, Reddit Pixel, Wistia Video, OneTrust Cookie Consent, Factors.ai
Frameworks
HubSpot, jQuery
Platforms
AWS (DNS via awsdns), HubSpot
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of cookie consent mechanism

Analytics and tracking

Services
Google Analytics 4, HubSpot Analytics, LinkedIn Insight Tag, Facebook Pixel, Bing Ads, Reddit Pixel, G2 Crowd
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Facebook Ads, Bing Ads, Reddit Ads
Tracking pixels
Facebook Pixel, LinkedIn Insight Tag, Google Analytics 4, G2 Crowd Tracking
Marketing tools
HubSpot Marketing, Factors.ai
Transparency
good

Site quality

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

Key observations

  1. Website is a 404 error page for the requested URL but global header/footer and navigation point to moengage.com
  2. Content is mostly a branded 404 page with search functionality
  3. Main domain hashgrowth.org appears to be a redirect or alias for MoEngage marketing content
  4. Use of HubSpot CMS and marketing automation tools
  5. Strong presence of marketing and analytics tracking scripts
  6. Privacy and cookie policies are present on the main moengage.com domain
  7. No direct phone numbers or physical addresses found on this domain's 404 page
  8. Social media links point to official MoEngage accounts
Technical notes

Notes

The website is built on HubSpot CMS, integrating multiple third-party marketing and analytics tools including Google Analytics 4, Facebook Pixel, LinkedIn Insight Tag, and OneTrust for cookie consent. Hosting is via AWS, inferred from DNS nameservers. The site uses jQuery and modern JavaScript libraries for interactivity. Performance is moderate, with good mobile optimization but basic accessibility and SEO. The presence of extensive tracking scripts indicates a strong focus on marketing analytics. The 404 error page content limits content richness but the global header and footer provide navigation to the main MoEngage site. Technical risks include lack of DNSSEC and missing security headers, which could be addressed to improve 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. 72/100Medium26 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.