Skip to content
https://www.ikea.fr

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
DNS Records
2 A records, 17 ms lookup
REVIEW
2 A records, 17 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.208.234, 104.17.209.234
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6811:d0ea, 2606:4700::6811:d1ea
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: fallback.www.ikea.cc
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 17 ms
Got: 17 ms
A104.17.208.234, 104.17.209.234
AAAA2606:4700::6811:d0ea, 2606:4700::6811:d1ea
CNAMEfallback.www.ikea.cc
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 17 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 24 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 24 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
36 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

36
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
Redirect Chain
1 redirect(s), 219 ms total
PASS
1 redirect(s), 219 ms total
Info::
Single redirect
Got: https://www.ikea.fr → https://www.ikea.com/fr/fr/ (301)
Info::
Cross-domain redirect detected

https://www.ikea.fr

70 ms · HTTP/1.1

301

https://www.ikea.com/fr/fr/

149 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.ikea.fr30170 msHTTP/1.1cloudflare
2https://www.ikea.com/fr/fr/200149 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6811:d0ea, 2606:4700::6811:d1ea
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700::6811:d0ea, 2606:4700::6811:d1ea Connection Reachable (1 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ikea.fr/
301https://ikea.fr/

Preferred variant: www

HTTP → HTTPS

301http://www.ikea.fr/ https://www.ikea.fr/

Consistent

A+
Domain Intelligence
ikea.fr — via CSC CORPORATE DOMAINS INC., 23 years, 5 months old
PASS
ikea.fr — via CSC CORPORATE DOMAINS INC., 23 years, 5 months old
Info::
Domain registered until Feb 11, 2027 (10 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: CSC CORPORATE DOMAINS INC.
Domain expiry

214 days

February 11, 2027

SSL certificate

36 days

Issued by Google Trust Services

Domain age

23 years, 5 months

Registered February 11, 2003

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:29c

Registrar

CSC CORPORATE DOMAINS INC.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar CSC CORPORATE DOMAINS INC.
Created February 11, 2003 (23 years, 5 months ago)
Expires February 11, 2027 (10 months)
Last Updated February 12, 2026
Name Servers udns1.cscdns.net, udns2.cscdns.uk
DNSSEC Enabled
Registrant Inter IKEA Systems B.V.
Hosting
IP Address 2606:4700::6812:29c
Data source: rdap (0.1s)
A+
HTTP Probe Timing
Total 84 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
15 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
13 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
84 ms
Total Time Total request time from DNS lookup through full response.
84 ms

Connection waterfall

DNS Lookup 15 ms TCP Connect 1 ms TLS Handshake 13 ms Server Processing 55 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9e8bc716ccf50a79-AMS
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9e8bc716ccf50a79-AMS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback