backmarket.de

Readiness by lane

Green: backmarket.de. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for backmarket.de

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 183 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   32% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   CAA records limit who can issue certificates

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

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

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DNSSEC signed

   Observed: No DS record was found for backmarket.de at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.

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

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

4. Priority 4 · Harden

   Referrer-Policy set

   Observed: The homepage response did not include a Referrer-Policy header.

   What to do: Send Referrer-Policy: strict-origin-when-cross-origin unless you have a reason to share more.

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

   Guide: A Practical Website Health Check for Owners

What backmarket.de already does well

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

• security.txt publishedsecurity.txt with a contact found.7.6% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers
• Reachable over IPv6IPv6 address published.40% of peers

What we saw

Homepage checked

https://www.backmarket.de/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-04

CDN or edge

Cloudflare, Google edge

Platform or framework

Nuxt

DNS operators

Cloudflare

HSTS

max-age 183 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

1,057 KB, br

Images on homepage

181 (png 1363, svg 436, jpg 404, webp 30)

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

Compare with other E-Commerce & Marketplaces sites

• backmarket.co.uk87
• backmarket.es87
• backmarket.fr87
• taniaksiazka.pl88
• vastranand.in88

E-Commerce & Marketplaces readiness benchmark