Skip to main content

Security report for loreal-paris.ee

L'Oréal Paris · Retail · Estonia

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

Security score

71/100

Risk levelMedium

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

L'Oréal Paris Estonia operates as a regional website for the globally recognized L'Oréal S.A., offering a wide range of cosmetics, skincare, and haircare products. The site targets general consumers interested in beauty and personal care, providing product information and editorial content such as the Beauty Magazine. The business model is retail-focused with an e-commerce presence, supported by a strong brand reputation and consistent branding across digital assets. Technically, the website employs modern JavaScript frameworks like Vue.js, integrates Google Tag Manager for analytics, and uses OneTrust for cookie consent, reflecting a mature digital infrastructure. Security posture is robust with HTTPS enforced, security headers present, and no critical vulnerabilities detected. Privacy compliance is well addressed through visible cookie consent mechanisms and a comprehensive privacy policy, aligning with GDPR requirements. Overall, the website demonstrates high professionalism, trustworthiness, and technical competence, though it lacks explicit security policy and incident response disclosures.

Scanned

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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, YouTube, Cloudflare

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

  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 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. 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 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 loreal-paris.ee

This scan found 18 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
65
Security headers
65
Email security
85
DNS health
70
Network security
100
GDPR outside view
40
Average
71

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

L'Oréal Paris holds a leading position in the cosmetics retail sector, leveraging its parent company L'Oréal S.A.'s global brand strength. The website serves as a localized platform for the Estonian market, focusing on product promotion and consumer engagement. Revenue streams likely include direct product sales and brand marketing. The target audience spans general consumers interested in beauty products, with content tailored to local language and preferences. The company benefits from a broad partnership ecosystem, including global marketing and analytics providers. Strategic observations highlight the importance of maintaining brand consistency and enhancing security transparency to reinforce consumer trust.

Security posture

The website exhibits a mature security posture with enforced HTTPS, presence of key security headers, and no visible exposure of sensitive data. The integration of cookie consent tools indicates compliance with privacy regulations. However, the absence of a dedicated security policy page and incident response contact information suggests room for improvement in transparency and preparedness. No vulnerability disclosure program or security.txt file was found, which could enhance responsible vulnerability management. Overall, the security maturity is good but could be elevated by formalizing security governance and communication.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Provide clear incident response contact channels such as security@ or abuse@ email addresses.
  3. Implement a vulnerability disclosure program and publish a security.txt file.
  4. Enhance website accessibility features to improve inclusivity.
  5. Regularly audit and update third-party scripts to mitigate supply chain risks.

Contact details published on the site

Addresses
Legal name
L'Oréal S.A.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
L'Oréal Paris
Description
L'Oréal S.A. is a French personal care company
Key services
Makeup products, Skincare products, Haircare products, Beauty Magazine content
Content quality
good
Branding
consistent

Technology

Stack
Vue.js 3.5.4, Google Tag Manager, OneTrust Cookie Consent, Yieldify, CDNJS
Frameworks
Vue.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager with consent

Analytics and tracking

Services
Google Analytics (via GTM)
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Yieldify
Marketing tools
Yieldify
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and well-branded for L'Oréal Paris Estonia.
  2. Comprehensive cookie consent and privacy mechanisms are implemented.
  3. Use of modern JavaScript frameworks and analytics tools.
  4. No critical security issues or blocking detected.
  5. Contact information is available but no explicit security policy or incident response details.
  6. No vulnerability disclosure or security.txt found.
Technical notes

Notes

The website uses a modern front-end framework (Vue.js 3.5.4) and integrates industry-standard analytics and consent management tools. The presence of preloaded fonts and deferred JavaScript loading suggests performance optimization efforts. SEO is supported by comprehensive meta tags, Open Graph, and JSON-LD structured data. Mobile optimization is good, with responsive design elements detected. Hosting details are not explicit, but the use of CDNs and external services indicates a distributed infrastructure. Technical risks are minimal, though continuous monitoring of third-party dependencies is advised to prevent vulnerabilities.
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 loreal-paris.ee. 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 loreal-paris.ee.

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.