Skip to main content

Security report for dior.com

Other · N/a

Medium risk. 6 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

75/100

Risk levelMedium

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

The website www.dior.com is currently inaccessible, returning a 'Page unavailable' error page with minimal content and no metadata or business information. The WHOIS lookup for the domain failed to return any registrar or registrant data, indicating either domain non-existence, privacy protection, or misconfiguration. Due to the lack of accessible content and absence of technical or business data, a comprehensive analysis of the company's digital presence and security posture is not possible. The site appears to be blocked by a web application firewall or similar security mechanism, which prevents content retrieval and analysis. From a technical perspective, no technologies, scripts, or frameworks could be identified. No security headers or SSL configuration details are available, and no privacy or cookie policies were found. The absence of contact information and business details further limits the ability to assess compliance or trustworthiness. Security posture is currently unknown but likely poor due to the lack of visible security best practices and the blocking of content. The domain's WHOIS data absence raises concerns about legitimacy and transparency. Overall, the site scores very low on content quality, technical implementation, security, privacy compliance, and business credibility. Strategic recommendations include resolving domain registration transparency issues, ensuring the website is accessible without blocking mechanisms for legitimate users, implementing and publishing privacy and security policies, and enhancing technical infrastructure to support secure and compliant operations.

Scanned

NIS2 and GDPR posture

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

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

Keep watching dior.com

This scan found 15 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
62
Security headers
75
Email security
85
DNS health
80
Network security
100
GDPR outside view
50
Average
75

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention dior.com, from OffSeq Breach.

Total records
10,230
Employees
0
Customers
10,153
Third parties
77
Weak passwords
6%

25 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for dior.com.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Brand lookalikes

Add-on

Domains that imitate dior.com and could be used for phishing or spoofed email, tracked in OffSeq Breach.

Tracked
105
Registered
105
Resolving
105
High or critical
0

Last checked 2026-07-05

Masked preview

  • xn•••••••••.comMediumhomoglyph
  • li•••.comMediumbitsquatting
  • dy•••.comMediumbitsquatting

See the full lookalike list

A one-off add-on that lists up to 20 of the highest-risk lookalikes of dior.com with registration, mail-server, certificate and DNS signals.

Select it in the checkout above.

Lookalike data refreshes continuously. Monitoring on Breach alerts you when a variant is registered, gains a mail server or starts serving HTTPS.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Due to the unavailability of website content and WHOIS data, no meaningful business intelligence can be derived. The domain www.dior.com is associated with a globally recognized luxury brand in reality, but this analysis is limited strictly to the provided data, which shows no accessible content or business information. No market positioning, revenue streams, or partnership data could be identified from the current dataset.

Security posture

The security posture cannot be fully assessed due to the lack of accessible content and metadata. The presence of a blocking error page suggests a web application firewall or security mechanism is active, which may protect the site but also hinders analysis. No security headers or SSL details were found. The absence of privacy policies and contact information for incident response indicates gaps in compliance and transparency. The domain's WHOIS data absence further reduces trust and raises potential legitimacy concerns.

Recommendations

  1. Resolve WHOIS registration issues to provide transparent domain ownership information.
  2. Ensure the website is accessible to legitimate users without triggering WAF blocks or error pages.
  3. Implement and publish comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  4. Deploy standard security headers and enforce HTTPS to improve security posture.
  5. Provide clear contact and incident response information to enhance trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. The website returns a 'Page unavailable' error with minimal HTML content and a reference ID, indicating likely blocking by a WAF or security mechanism. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible and returns a 'Page unavailable' error.
  2. No metadata, Open Graph, or structured data found in HTML.
  3. No forms, contact information, or external links present.
  4. No scripts or technologies detected from the minimal HTML.
  5. WHOIS data is missing or unavailable, indicating possible domain registration issues.
  6. Likely presence of a WAF or security mechanism blocking access.
  7. No privacy, cookie, or terms of service policies detected.
  8. No security headers or SSL configuration information available.
  9. No business or branding information available from the content.
Technical notes

Notes

The website currently serves only a minimal error page with no metadata, scripts, or detectable technologies. No CMS, frameworks, or hosting provider information could be identified. The lack of content and technical details suggests either a misconfigured or offline site. Performance, mobile optimization, accessibility, and SEO cannot be evaluated. The domain's WHOIS data is missing, indicating potential registration or privacy issues. Overall, the technical infrastructure appears incomplete or inaccessible.
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 dior.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 dior.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.