STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

bonprix.at

bonprix.at's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.

Readiness index
88/100

E-Commerce & Marketplaces median 71

Ahead of
99%

of measured E-Commerce & Marketplaces 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:01:51 UTC from one location. How we measure

Readiness by lane

Green: bonprix.at. Thin bar: E-Commerce & Marketplaces peer median.

Enable

95/100

Peers 86

Harden

75/100

Peers 60

Accelerate

100/100

Peers 69

Recover

100/100

Peers 11

Priority fixes for bonprix.at

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

  1. Priority 1 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.

    Why it matters: Under CA/Browser Forum Ballot SC-081v3, the maximum lifetime of public TLS certificates fell to 200 days on 15 March 2026 and falls to 100 days on 15 March 2027 and 47 days on 15 March 2029. Sites that renew by hand will need to renew far more often.

    What to do: Move to automated issuance and renewal now, while you still have time to test it.

    70% of E-Commerce & Marketplaces peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for bonprix.at, 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.

    16% of E-Commerce & Marketplaces 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.

    7.6% of E-Commerce & Marketplaces peers do this.

  4. Priority 4 · Enable

    Reachable over IPv6

    Observed: No IPv6 (AAAA) address was published for www.bonprix.at.

    What to do: Enable IPv6 at your CDN or host and publish the AAAA record it provides.

    40% of E-Commerce & Marketplaces peers do this.

What bonprix.at already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

  • Nameservers spread across providersNameservers spread across more than one operator.11% of peers
  • HSTS kept for at least a yearHSTS with a 365-day max-age.32% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers

What we saw

Homepage checked
https://www.bonprix.at/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 197-day validity, expiring 2026-12-24
CDN or edge
Amazon CloudFront
DNS operators
2 self-run or other nameserver domains
HSTS
max-age 365 days
DMARC policy
p=reject
Homepage HTML
736 KB, gzip
Images on homepage
88 (jpg 424, svg 1)

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
  • 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
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage
  • Nameservers spread across providers

Own bonprix.at?

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: bonprix.at. This profile covers configuration only.

Compare with other E-Commerce & Marketplaces sites