roller.de

Readiness by lane

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

Priority fixes for roller.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: The homepage response did not include a Strict-Transport-Security header.

   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.

   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

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

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

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Enable

   Social preview image set

   Observed: The homepage had no og:image, so shared links may show without a preview image.

   What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

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

   Guide: SEO Checklist for a New Website

4. Priority 4 · Harden

   CAA records limit who can issue certificates

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

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

   Guide: HTTPS and TLS Guide for Website Owners

What roller.de 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
• Referrer-Policy setReferrer-Policy present.20% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers

What we saw

Homepage checked

https://www.roller.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Google edge

Platform or framework

Nuxt

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

337 KB, br

Images on homepage

46

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

• prashantisarees.com82
• reisemoto.com82
• rhodeskin.com82
• rosebikes.de82
• rossmann.pl82

E-Commerce & Marketplaces readiness benchmark