Skip to main content

Security report for helloretail.com

Hello Retail · E-commerce · N/a

Medium risk. 5 critical or high findings in Security headers, SSL/TLS and 1 other check.

Security score

58/100

Risk levelMedium

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

Hello Retail is a medium-sized e-commerce personalization SaaS provider founded in 2015. The company targets online retailers seeking to enhance customer experience and increase sales through personalized marketing solutions. The website is professionally designed using WordPress and Elementor, integrating modern marketing and analytics tools such as HubSpot, Google Tag Manager, Facebook Pixel, and Cookiebot for consent management. The technical infrastructure is solid, hosted likely on AWS infrastructure, with good mobile optimization and SEO practices. Security posture is adequate with HTTPS enabled and use of reCAPTCHA, but lacks some advanced security headers and DNSSEC. Privacy compliance is partial, with cookie consent implemented but no explicit privacy or terms of service pages detected. Overall, the website is trustworthy and business credible but could improve transparency on privacy and security policies.

Scanned

NIS2 and GDPR posture

GDPR outside view
95/ 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

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

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

Keep watching helloretail.com

This scan found 24 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
62
Security headers
15
Email security
75
DNS health
80
Network security
20
GDPR outside view
95
Average
58

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

Hello Retail operates in the e-commerce sector providing personalization technology as a SaaS business model. Their competitive advantage lies in integrating multiple marketing and analytics platforms to deliver tailored customer experiences. The company appears to focus on B2B clients in the retail e-commerce space, leveraging partnerships with marketing platforms like HubSpot and Trustpilot. The domain age and technical sophistication indicate a mature business with a stable market presence. However, the lack of explicit contact information and privacy policies may limit trust for some customers. Growth indicators include extensive use of tracking and marketing tools, suggesting active customer engagement and data-driven strategies.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and use of Google reCAPTCHA v3 to protect forms. Cookie consent is managed via Cookiebot, indicating awareness of privacy regulations. However, the absence of DNSSEC, security.txt, and explicit security or incident response policies indicates gaps in security governance and transparency. No vulnerabilities or exposed sensitive data were detected in the HTML content. Security headers appear minimal or not explicitly set, which could be improved to harden the site against common web attacks. Incident response readiness is not publicly documented, which could impact trust and compliance with regulations like GDPR or NIS2.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a comprehensive privacy policy and terms of service pages to enhance compliance and user trust.
  3. Implement and verify security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Create and publish a security policy and incident response contact information to improve transparency and readiness.
  5. Add a vulnerability disclosure policy or security.txt file to encourage responsible reporting and improve security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Hello Retail
Description
Hello Retail provides personalization solutions for e-commerce businesses to enhance customer experience and increase sales.
Key services
Personalization software, Customer experience enhancement, E-commerce analytics
Content quality
good
Branding
consistent

Technology

Stack
Google Tag Manager, Facebook Pixel, HubSpot, Cookiebot, Google reCAPTCHA v3, Trustpilot, Hotjar, Elementor, WordPress
Frameworks
Elementor
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Use of reCAPTCHA v3
  • Cookie consent mechanism
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, HubSpot Analytics, Hotjar, Plausible
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Facebook Ads, Google Ads
Tracking pixels
Facebook Pixel, HubSpot Analytics, Hotjar
Marketing tools
HubSpot, Sleeknote, Trustpilot
Transparency
good

Site quality

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

Key observations

  1. Website uses modern marketing and analytics tools.
  2. No explicit privacy or terms of service pages detected in the provided content.
  3. Cookie consent mechanism is implemented via Cookiebot.
  4. No direct contact emails or phone numbers found in the HTML content.
  5. Website is built on WordPress with Elementor page builder.
  6. No security.txt or vulnerability disclosure found.
  7. No explicit security or incident response policies published.
  8. Website content is professional and targeted at e-commerce businesses.
Technical notes

Notes

The website is built on WordPress using the Elementor page builder, integrating multiple third-party marketing and analytics scripts including HubSpot, Facebook Pixel, Google Tag Manager, and Cookiebot. Hosting appears to be on AWS infrastructure with domain registration via Amazon Registrar, Inc. Performance is moderate with good mobile optimization and SEO practices. The site uses modern fonts and preconnects to optimize resource loading. Technical debt appears low, but security enhancements such as DNSSEC and security headers are missing. The extensive use of tracking scripts indicates a data-driven approach but requires careful privacy management. Overall, the technical infrastructure supports a professional e-commerce SaaS business but could benefit from security and privacy improvements.
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. 56/100Medium33 findingsView report
Reviews of this site

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