Skip to main content

Security report for maje.com

Maje · Retail · France

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

68/100

Risk levelMedium

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

Maje is a global fashion retail brand operating a multi-regional e-commerce platform with localized websites for numerous countries and languages. The website serves as a landing page directing users to country-specific stores, indicating a broad international market presence. The business model focuses on online retail of clothing and accessories, targeting fashion consumers worldwide. The site is built on Salesforce Commerce Cloud (Demandware), leveraging modern e-commerce infrastructure. Technically, the website employs JavaScript, jQuery, Google Tag Manager, and CQuotient for analytics and marketing. The platform is mobile optimized with responsive design and moderate performance. However, some technical misconfigurations are present, such as an invalid Google Tag Manager container ID. No explicit security headers were detected in the provided HTML, and privacy or cookie policies are absent from the landing page, indicating gaps in compliance and security best practices. From a security perspective, the site uses HTTPS (implied but not explicitly confirmed in the snippet), but lacks visible security headers and privacy compliance indicators. The WHOIS lookup failed to retrieve domain registration data, which is unusual for an established brand and lowers trustworthiness. No contact information or incident response details are provided on the landing page, limiting transparency. No adult or explicit content is present, making the site safe for general audiences. Overall, the website is functional and professionally designed but requires improvements in security posture, privacy compliance, and domain registration transparency to enhance trust and regulatory adherence.

Scanned

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

NIS2 and GDPR posture

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

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

    • 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 maje.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
77
Security headers
55
Email security
60
DNS health
80
Network security
100
GDPR outside view
35
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

Maje positions itself as a mid-to-high-end fashion retailer with a strong international footprint, evidenced by multiple localized domains serving different countries and languages. The business leverages e-commerce to reach a broad consumer base, focusing on apparel and accessories. The use of Salesforce Commerce Cloud indicates investment in scalable, enterprise-grade e-commerce technology. The absence of visible contact or compliance information on the landing page suggests a potential area for improvement in customer trust and regulatory compliance. The brand's market presence is solid, but the WHOIS data inconsistency could raise questions among security-conscious stakeholders. The company likely generates revenue through direct online sales and possibly through partnerships with regional distributors or marketplaces.

Security posture

The current security posture shows moderate maturity. HTTPS is presumably enabled, but no security headers such as Content Security Policy, HSTS, or X-Frame-Options were detected, which are important for mitigating common web attacks. The Google Tag Manager implementation is misconfigured, which could lead to tracking or security issues. The lack of privacy and cookie policies on the landing page indicates non-compliance with GDPR and other privacy regulations, posing legal risks. No incident response or security contact information is provided, limiting the ability to report or respond to security incidents. Overall, the site would benefit from enhanced security headers, proper privacy disclosures, and improved transparency to strengthen its security culture and compliance posture.

Recommendations

  1. Implement comprehensive privacy and cookie policies clearly accessible from all landing pages to improve GDPR compliance.
  2. Configure Google Tag Manager with a valid container ID to ensure proper analytics and reduce security risks.
  3. Add standard security headers (CSP, HSTS, X-Frame-Options, X-Content-Type-Options) to harden the website against common attacks.
  4. Publish clear contact information including security incident response contacts to improve transparency and trust.
  5. Investigate and resolve WHOIS data unavailability to enhance domain registration transparency and legitimacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Maje
Description
Maje is a fashion retail brand offering clothing and accessories, targeting a global audience with localized websites for multiple countries and languages.
Key services
Online retail of clothing and fashion accessories
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, jQuery, Google Tag Manager, Demandware (Salesforce Commerce Cloud), CQuotient
Frameworks
Demandware (Salesforce Commerce Cloud)
Platforms
Salesforce Commerce Cloud
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Use of Google Tag Manager
  • No visible exposed sensitive data in HTML

Analytics and tracking

Services
Demandware Analytics, Google Tag Manager, CQuotient
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
CQuotient
Marketing tools
CQuotient
Transparency
basic

Site quality

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

Key observations

  1. Website is a multi-regional fashion e-commerce landing page
  2. No privacy, cookie, or terms of service policies found on landing page
  3. No contact emails or phone numbers visible on landing page
  4. Google Tag Manager is included but with invalid container ID
  5. No security headers detected in provided HTML snippet
  6. WHOIS data unavailable, possibly due to privacy or registry issues
  7. Site uses Salesforce Commerce Cloud platform
  8. Mobile optimized with responsive design
  9. No adult or explicit content detected
Technical notes

Notes

The website is built on Salesforce Commerce Cloud (Demandware), a robust e-commerce platform supporting multi-regional deployments. The tech stack includes JavaScript, jQuery, Google Tag Manager, and CQuotient for analytics and marketing. The site is mobile responsive and uses modern CSS and HTML practices. However, the Google Tag Manager ID is set to 'null', indicating a configuration error. No explicit security headers were found in the HTML snippet, which is a technical gap. Performance appears moderate based on the use of asynchronous script loading and responsive images. SEO is basic with meta description and keywords present but no advanced structured data or Open Graph tags detected. Accessibility features are minimal but basic usability is supported. Overall, the technical implementation is solid but could be improved with better security and privacy configurations.
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/100Medium29 findingsView report
  2. 71/100Medium29 findingsView report
Reviews of this site

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