dior.cn

We performed a comprehensive analysis of dior.cn on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 14220ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 463 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-09-21, which is 83 days from now. The security headers analysis reveals a score of 65/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Content-Security-Policy and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 6 technologies across 6 categories powering dior.cn. The detected stack includes Magento, Next.js css, React, Webpack, Google Tag Manager, and Google Fonts. The primary e-commerce platform is Magento. The site uses Next.js as its primary framework (version css). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, dior.cn receives an overall trust score of 79/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, dior.cn receives a trust score of 79/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Let's Encrypt with 83 days until expiration, and DMARC email authentication with a reject policy — the strongest available setting. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked dior.cn against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned dior.cn and identified 6 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Ecommerce: Magento — powers the online store and shopping functionality for dior.cn. Framework: Next.js (version css) — provides the application framework and routing for dior.cn. UI Library: React — handles the user interface rendering and component management for dior.cn. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for dior.cn. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for dior.cn. Fonts: Google Fonts — delivers web fonts for typography for dior.cn. We also extracted the following tracking identifiers: Google Tag Manager container GTM-PN3F34N. These IDs can be used to identify other websites operated by the same organization.

dior.cn delivers its homepage in 14220ms (server response time), which is considered slow by industry standards. The total page weight is 463 KB, and we detected 127 resource requests loading assets from 11 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. Asset minification status: 0 out of 2 CSS files and 0 out of 21 JavaScript files are minified. Minifying the remaining 23 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. From an environmental perspective, each page view of dior.cn produces approximately 0.23g of CO₂, earning a carbon rating of B. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 463 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for dior.cn. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

dior.cn resolves to the IPv4 address 185.16.44.89, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 1 A record(s) configured. The domain name system is managed by 6 name servers: a.ns.domainoo.fr, a1-1.akam.net, a18-66.akam.net, a20-67.akam.net, a26-64.akam.net, and b.ns.domainoo.fr. Having 6 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for dior.cn is handled by domainoo.fr with 1 MX records configured: a.mx.domainoo.fr. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for dior.cn. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions. Our subdomain enumeration scan discovered 2 active subdomains for dior.cn: m.dior.cn and www.dior.cn. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of dior.cn contains 43 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 2 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 5 images. 2 images (40%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 60% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 16 internal links pointing to other pages on the same domain and 7 external links pointing to third-party websites. There are 21 external JavaScript files, 2 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and Schema.org structured data (BreadcrumbList and ListItem). Notable missing features: XML Sitemap. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on dior.cn: American Express, Discover, Alipay, Apple Pay, Google Pay, and Klarna. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for dior.cn is well-optimized at 31 characters: "DIOR - 中国官方网上商店 | 时尚与美容 | DIOR". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 63 characters (acceptable): "在中国探索克里斯汀-迪奥 (CD) 的世界：所有男女时装：手袋、成衣、珠宝和手表、高级定制时装，所有美容：香水、化妆品、护肤品". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The canonical url is correctly set to https://www.dior.cn/zh_cn, preventing duplicate content issues, the page language is declared as zh-cn, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("DIOR - 中国官方网上商店 | 时尚与美容 | DIOR..."), OG description, OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. The site implements Schema.org structured data with the following types: BreadcrumbList and ListItem. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.