STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

liebherr.com

liebherr.com's public homepage, certificate and DNS checked against 31 practices and compared with 703 Cars & Automotive sites.

Readiness index
86/100

Cars & Automotive median 66

Ahead of
97%

of measured Cars & Automotive sites

Practices observed
25/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:12:06 UTC from one location. How we measure

Readiness by lane

Green: liebherr.com. Thin bar: Cars & Automotive peer median.

Enable

82/100

Peers 84

Harden

80/100

Peers 57

Accelerate

100/100

Peers 65

Recover

100/100

Peers 14

Priority fixes for liebherr.com

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Enable

    Canonical URL declared

    Observed: The homepage did not declare a canonical URL.

    Why it matters: A canonical link tells search engines which URL to show when the same page is reachable at several addresses.

    What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

    79% of Cars & Automotive peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

  2. Priority 2 · Enable

    At most one redirect to the homepage

    Observed: The homepage was reached after 3 redirects.

    What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.

    98% of Cars & Automotive peers do this.

  3. Priority 3 · Harden

    security.txt published

    Observed: No valid /.well-known/security.txt with a Contact field was returned.

    What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

    On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

    8.9% of Cars & Automotive peers do this.

  4. Priority 4 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for liebherr.com, so any public certificate authority may issue for it.

    What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

    On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

    7.8% of Cars & Automotive peers do this.

What liebherr.com already does well

Practices fewer than half of Cars & Automotive peers use.

  • Nameservers spread across providersNameservers spread across more than one operator.14% of peers
  • HTTP/3 advertisedHTTP/3 advertised.30% of peers
  • Content Security Policy presentContent-Security-Policy present.31% of peers

What we saw

Homepage checked
https://www.liebherr.com/
Homepage response
HTTP 200, after 3 redirects
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-12-09
CDN or edge
Cloudflare
Platform or framework
Next.js
DNS operators
3 self-run or other nameserver domains
HSTS
max-age 365 days, includeSubDomains
DMARC policy
p=reject
Homepage HTML
320 KB, br
Images on homepage
27 (jpg 47, webp 25, svg 6, png 4)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Observed 25

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • Nameservers spread across providers

Own liebherr.com?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: liebherr.com. This profile covers configuration only.

Compare with other Cars & Automotive sites