Home › Guides › dior.com — domain analysis
Guide

dior.com — domain analysis

✎ Independent, reader-supported guide — information, not financial advice. Crypto card terms change often; confirm current details with the issuer.

dior.com blocks automated analysis, answering with HTTP 403 to an automated client instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below.

This site blocks automated analysis.
It answered our request with HTTP 403 to an automated client rather than its
homepage, so nothing below is derived from its actual content — doing so would describe
the bot wall, not the site. The certificate and robots.txt data are still accurate,
because those are served to everyone.

403HTTP status
161msResponse time
0Words on the homepage
0/6Security headers set

How does dior.com compare with other domains analysed here?

Measured against the 74 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.

Response time Faster than 78% of them
(median 463ms)
Domain age Older than 84% of them

Related domains in this index

Other domains analysed in this index:

When was dior.com registered?

dior.com was registered on 6 October 1995, which makes it about 30 years old.

A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.

The registrar of record is Register.com – Network Solutions, LLC.

Registration runs until 5 October 2027.

The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.

Registered 6 October 1995
Expires 5 October 2027
Registrar Register.com – Network Solutions, LLC
Registry status client transfer prohibited

Where is dior.com hosted?

The first address resolves to infrastructure in Ostwald, France.

The network is operated by Planet Service SARL (AS61168 Planet Service SARL).

Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.

What is dior.com running on?

No platform, framework or analytics fingerprints were found in the homepage markup of dior.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.

No recognisable platform, framework or analytics fingerprints were found in the homepage markup.

How does the homepage respond?

The server answered with HTTP 403 over
HTTPS.

At 161ms to first byte this response is fast for a homepage measured from a single European location.

At 1KB the HTML is unusually small, which typically means the page builds itself client-side after load.

No compression is applied to the HTML. Enabling gzip or brotli usually cuts transfer size by around two thirds at no cost to the server.

Server header AkamaiGHost
Compression none
Page size 754 bytes
Declared language not declared
Mobile viewport not declared

What does the homepage say about itself?

The homepage has no title element at all, which leaves search engines to invent one from the page content.

There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.

No H1 heading was found, so the page offers no single top-level statement of what it is.

No viewport meta tag is declared, so mobile browsers will render the page at desktop width and scale it down.

The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.

Title — none — (0 chars)
Meta description — none — (0 chars)
H1 — none — (0 on the page)
Canonical not set
Open Graph title not set
Headings / images 0 H2s, 0 images (0 without alt text)

Is dior.com served over a valid certificate?

The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-11-18, which is 44 days from the date of this check. It covers
1 hostname.

  • dior.com

The certificate has 44 days left to run.

It covers 1 hostname, so it was issued for this site specifically.

Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.

Which security headers does it set?

None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.

Header Set Value

How is DNS configured for dior.com?

IP addresses 185.16.44.89
Reverse DNS 0.redirect-lets-encrypt.domainoo.com
Name servers a9-66.akam.net, a1-1.akam.net, c.ns.domainoo.fr, b.ns.domainoo.fr, a18-66.akam.net, a7-65.akam.net, a20-67.akam.net, a.ns.domainoo.fr, a26-64.akam.net
Mail (MX) mxa-0024c501.gslb.pphosted.com (pri 10), mxb-0024c501.gslb.pphosted.com (pri 10)
SPF v=spf1 ip4:151.106.145.158 ip4:160.8.96.30 ip4:91.216.209.209 ip4:90.83.117.241 ip4:83.167.45.110 ip4:46.18.135.73 ip4:18.196.215.67 ip4:104.161.152.5 mx a:emailing.christiandior.fr a:production.eu01.dior.demandware.net a:production.eu02.dior.demandware.net include:trustpilotservice.com include:spf.mandrillapp.com include:sendgrid.net include:_spf.salesforce.com -all
TXT records 25

dior.com resolves to a single address, so there is no DNS-level redundancy.

Mail is handled by 2 exchangers.

An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.

Reverse DNS resolves to 0.redirect-lets-encrypt.domainoo.com, which usually names the hosting provider.

Can dior.com be spoofed in email?

DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.

No CAA records are published, so any certificate authority may issue a certificate for this domain.

The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.

What does robots.txt allow?

No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.

What structured data does the homepage publish?

No JSON-LD or microdata was found on the homepage.

Frequently asked questions

Does dior.com allow AI crawlers?

No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.

Where does this data come from?

Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.

Is any of this traffic or authority data?

No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.

I own dior.com and want this page removed.

Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.

Analysed 5 October 2026.
Analyse another domain →

Related guides