Skip to main content

Security report for shoplazzastatus.com

Shoplazza · E-commerce · N/a

Medium risk. 6 critical or high findings in Email security, Security headers and 2 other checks.

Security score

68/100

Risk levelMedium

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

Shoplazza Status is a dedicated status page for the Shoplazza e-commerce platform, providing real-time and historical system performance data. The website is professionally designed, mobile-optimized, and leverages Atlassian Statuspage technology to deliver transparent operational status updates. The platform targets e-commerce merchants and users who rely on Shoplazza's services for storefront, checkout, API, reporting, and third-party integrations. The business model is SaaS-based, focusing on providing reliable e-commerce infrastructure and transparency to its customers. Technically, the site uses modern web technologies including jQuery, Google reCAPTCHA Enterprise for form security, and is hosted on Amazon Cloudfront CDN ensuring fast performance and global availability. The site is well-structured with good SEO and accessibility features, though it lacks some advanced security headers. The forms for subscription to incident updates are secured with reCAPTCHA, indicating a focus on preventing abuse. From a security perspective, the site enforces HTTPS and uses reCAPTCHA to protect forms, but lacks visible security headers such as CSP or HSTS. No exposed sensitive data or vulnerabilities were detected in the HTML content. However, the absence of WHOIS registration data for the domain raises concerns about domain legitimacy and trustworthiness. The privacy policy is present and indicates GDPR compliance, but cookie policy and terms of service are missing. Contact information and incident response details are not provided, limiting transparency in security and compliance. Overall, the website presents a professional and secure front for status reporting but would benefit from enhanced transparency in domain registration, security policies, and contact information. Strategic improvements in security headers, cookie consent, and incident response contact details would strengthen trust and compliance posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 100 · Medium
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

6 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…

  3. 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 shoplazzastatus.com

This scan found 23 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
72
Security headers
50
Email security
60
DNS health
70
Network security
100
GDPR outside view
58
Average
68

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

Shoplazza operates as a medium-sized e-commerce platform provider with a focus on operational transparency through its status page. The company targets online merchants requiring reliable storefront, payment, API, and reporting services. The use of Atlassian Statuspage indicates a mature approach to incident communication. The lack of WHOIS data suggests either recent domain registration or privacy protection, which may impact trust. The business model is SaaS with revenue likely from subscriptions or service fees. The absence of direct contact details on the status page suggests that customer support is handled elsewhere, possibly on the main Shoplazza site. The partnership with Atlassian for status management is a positive indicator of integration with established enterprise tools. Growth indicators and parent/subsidiary relationships are not evident from the data provided.

Security posture

The security posture of the Shoplazza status site is solid in terms of HTTPS enforcement and use of Google reCAPTCHA Enterprise to protect subscription forms from abuse. No sensitive data leakage or vulnerable libraries were detected. However, the absence of common security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces the overall security hardening. The lack of explicit security or incident response policies and absence of contact channels for security issues limits the site's readiness for incident management and transparency. The missing WHOIS data for the domain is a notable concern, as it reduces trust in domain legitimacy. Overall, the site demonstrates good baseline security but requires enhancements in headers, policy transparency, and domain registration clarity.

Recommendations

  1. Implement standard security headers including CSP, HSTS, and X-Frame-Options to improve security posture.
  2. Publish a cookie policy and implement a consent mechanism to comply with privacy regulations.
  3. Provide clear contact information and incident response channels for security and abuse reporting.
  4. Clarify domain registration details or ensure WHOIS data is publicly available to enhance trust.
  5. Add terms of service and vulnerability disclosure policy to improve transparency and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Shoplazza
Description
Shoplazza provides real-time and historical data on system performance for its e-commerce platform.
Key services
Checkout And Payment, Storefront, OpenApi, Reports And Dashboards, Account And Admin, Third party services
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.5.1, Atlassian Statuspage, Google reCAPTCHA Enterprise, Polyfill.io
Frameworks
Atlassian Statuspage
Platforms
Cloudfront CDN
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Google reCAPTCHA Enterprise for forms
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Google reCAPTCHA
Transparency
basic

Site quality

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

Key observations

  1. Website is a status page for Shoplazza e-commerce platform
  2. No WHOIS data available, domain may be newly registered or privacy protected
  3. Site uses Atlassian Statuspage platform for status reporting
  4. No contact emails or phone numbers explicitly provided on status page
  5. Privacy policy is linked and accessible
  6. No cookie policy or terms of service found on status page
  7. Site uses Google reCAPTCHA Enterprise for form security
  8. No security headers detected in HTML content
  9. No visible vulnerabilities or exposed sensitive data
  10. No advertising or affiliate marketing detected
Technical notes

Notes

The website is built on a modern and performant stack leveraging Atlassian Statuspage platform, jQuery 3.5.1, and Google reCAPTCHA Enterprise for security. It is hosted on Amazon Cloudfront CDN, ensuring fast global delivery. The site is mobile-optimized with responsive design and accessibility considerations. SEO is well addressed with proper meta tags and canonical links. The use of polyfills ensures compatibility with older browsers. No CMS is explicitly detected, indicating a custom or SaaS platform. The technical implementation is robust with no broken elements or errors detected. Opportunities exist to improve security headers and add more comprehensive privacy and security policies.
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

Reviews of this site

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