Skip to main content

Security report for heliumdev.com

Helium Development · E-commerce · N/a

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

Security score

58/100

Risk levelMedium

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

Helium Development is a small technology company specializing in building Shopify apps and providing website design and custom functionality services for e-commerce merchants. The company positions itself as a Shopify Expert, focusing on reliable and customer-centric software solutions to help online businesses grow. Their website content is professional and well-structured, targeting Shopify merchants and online retailers. Technically, the site uses modern JavaScript, CSS, and SVG technologies, with integrations for analytics and user behavior tracking via Google Tag Manager and Hotjar. The hosting is inferred to be on Netlify, and the site is optimized for mobile with good SEO practices. However, the website lacks a valid SSL certificate and does not serve content over HTTPS, which is a critical security issue. No security headers are present, and advanced SSL features like HSTS and OCSP stapling are missing. Privacy compliance is basic, with privacy and cookie policies present and a cookie consent mechanism implemented. Contact information is limited to a contact form, with no direct emails or phone numbers publicly listed. Overall, the site demonstrates moderate business credibility and technical maturity but requires urgent security improvements to protect user data and enhance trust.

Scanned

This is an earlier scan of heliumdev.com. View the latest report

NIS2 and GDPR posture

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

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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching heliumdev.com

This scan found 17 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
50
Security headers
30
Email security
50
DNS health
80
Network security
100
GDPR outside view
40
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

Helium Development operates in the e-commerce sector, focusing on Shopify app development and web design services. Their business model revolves around software sales and custom development for Shopify merchants, leveraging their Shopify Expert status as a competitive advantage. The company has been active since 2015 and maintains a professional online presence with clear service offerings. Their partnership with Shopify and use of Google Workspace and SendGrid for email infrastructure indicate a mature operational setup. The website's integration of multiple tracking and analytics tools suggests an emphasis on data-driven marketing and user experience optimization. However, the absence of direct contact details and limited public business information may impact customer trust. The company could benefit from enhanced transparency and stronger security posture to solidify its market position.

Security posture

The current security posture of heliumdev.com is weak due to the absence of a valid SSL certificate and lack of HTTPS support, exposing users to potential data interception risks. The site does not implement essential security headers, HSTS, or OCSP stapling, which are standard best practices for web security. While DNS records show proper email authentication with DMARC and no subdomain takeover vulnerabilities, the web-facing security controls are insufficient. No incident response or vulnerability disclosure information is publicly available, limiting transparency and preparedness. The use of third-party tracking scripts introduces additional risk vectors that require regular auditing. Immediate remediation of SSL/TLS issues and implementation of security headers are critical to improving the security posture and protecting user data.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Configure HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Enable HSTS with includeSubDomains and preload directives to enforce HTTPS.
  4. Implement OCSP stapling and session resumption to improve SSL performance and security.
  5. Publish a vulnerability disclosure policy or security.txt file to enhance transparency and incident response readiness.
Technical notes

Notes

The website is built using standard web technologies including JavaScript, CSS, and SVG graphics, with integrations for Google Tag Manager, Hotjar, and RB2B tracking scripts. The hosting environment is likely Netlify, inferred from DNS SOA and nameservers. The site has a relatively large page size (~580 KB) and slow load time (~21 seconds), indicating potential performance optimization opportunities. Mobile optimization is good, and SEO practices are well implemented with proper meta tags and Open Graph data. However, the lack of HTTPS and security headers represents a significant technical risk. The site does not use a CMS or known web frameworks explicitly. Overall, the technical infrastructure is functional but requires modernization and security hardening to meet current web standards.
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. 71/100Medium30 findingsView report
Reviews of this site

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