Skip to main content

Security report for stackla.com

Nosto · E-commerce · N/a

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

Security score

72/100

Risk levelMedium

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

Nosto is a commerce experience platform specializing in shoppable user-generated content (UGC) that helps e-commerce businesses convert authentic customer content into commerce opportunities. The company positions itself as a trusted provider in the e-commerce technology space, offering solutions that boost click-through rates, build trust, and increase customer loyalty. The website is professionally designed, mobile-optimized, and uses modern web technologies including Google Fonts, Typekit, Swiper.js, Marketo forms, Google Tag Manager, reCAPTCHA, and Intercom for customer engagement and analytics. From a security perspective, the website enforces HTTPS and uses reCAPTCHA to protect forms, indicating a good baseline security posture. However, explicit security headers and a dedicated security policy or incident response page are not publicly available, which could be improved to enhance trust and compliance. The absence of WHOIS data limits the ability to fully verify domain legitimacy, but the professional web presence and social media links support the business's credibility. Overall, the website is well-structured, SEO-optimized, and provides a positive user experience. The business appears legitimate and focused on serving e-commerce clients with advanced marketing technology solutions. Strategic recommendations include publishing detailed security and incident response policies and improving transparency around domain registration details.

Scanned

NIS2 and GDPR posture

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

4 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 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
    • 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 stackla.com

This scan found 21 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
42
Security headers
30
Email security
80
DNS health
90
Network security
100
GDPR outside view
88
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

Nosto operates in the e-commerce sector, targeting online retailers and brands seeking to leverage user-generated content for commerce. Its business model is B2B SaaS, providing a platform that integrates with e-commerce sites to enhance customer engagement and sales. The company benefits from a consistent brand presence and active social media channels, which support its market positioning. While direct contact details are limited on the analyzed page, the presence of contact forms and marketing tools like Marketo and Intercom indicate a mature marketing and sales process. The lack of WHOIS data is a minor concern but does not detract significantly from the overall business credibility.

Security posture

The website demonstrates a solid security foundation with HTTPS and form protection via reCAPTCHA. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options, and the lack of a published security policy or incident response contact, represent gaps in the security posture. No vulnerabilities or exposed sensitive data were detected in the analysis. Compliance with GDPR is suggested by the presence of privacy and cookie policies with consent mechanisms. Enhancing transparency around security practices and incident handling would strengthen the security culture and trustworthiness.

Recommendations

  1. Publish a dedicated security policy page detailing security practices and controls.
  2. Implement and enforce security headers like Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Provide clear incident response contact information, such as a security@ or abuse@ email address.
  4. Improve transparency of domain registration details or clarify privacy protection usage.
  5. Maintain and regularly update privacy and cookie policies to ensure ongoing GDPR compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Nosto
Description
Nosto’s Shoppable UGC turns authentic customer content into commerce—boosting click-throughs, building trust, and increasing loyalty.
Key services
Shoppable User Generated Content (UGC), Commerce Experience Platform, Customer content monetization
Content quality
excellent
Branding
consistent

Technology

Stack
Google Fonts, Typekit Fonts, Swiper.js, Marketo Forms, Google Tag Manager, reCAPTCHA, Intercom
Performance
fast
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of reCAPTCHA on forms
  • Use of Intercom for support

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Intercom
Marketing tools
Marketo Forms, Intercom
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented and targeted at e-commerce businesses.
  3. No direct company contact emails or phone numbers found on the analyzed page; contact is via forms.
  4. WHOIS data is unavailable or domain may be privacy protected or unregistered under the queried name.
  5. Strong SEO and metadata implementation with Open Graph and JSON-LD structured data.
  6. Use of modern web technologies and marketing tools.
  7. No explicit security policy or incident response information publicly available.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on WordPress CMS and leverages modern front-end technologies including Google Fonts, Typekit, and Swiper.js for UI components. Marketing and analytics tools include Marketo forms, Google Tag Manager, Intercom, and reCAPTCHA, indicating a sophisticated digital marketing infrastructure. The site is mobile-optimized with responsive design and good accessibility features. Performance appears fast with asynchronous loading of scripts and optimized assets. SEO is well-implemented with comprehensive meta tags, Open Graph data, and JSON-LD structured data enhancing search engine visibility and social media integration. Opportunities exist to improve security headers and provide more detailed technical documentation on security and compliance.
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. 65/100Medium32 findingsView report
Reviews of this site

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