oetker.de

Readiness by lane

Green: oetker.de. Thin bar: Food & Grocery Delivery peer median.

Priority fixes for oetker.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.

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

   42% of Food & Grocery Delivery 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 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   63% of Food & Grocery Delivery peers do this.

   Guide: Structured Data Basics for Website Owners

3. Priority 3 · Harden

   CAA records limit who can issue certificates

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

   9.7% of Food & Grocery Delivery peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · 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.

   6% of Food & Grocery Delivery peers do this.

   Guide: A Practical Website Health Check for Owners

What oetker.de already does well

Practices fewer than half of Food & Grocery Delivery peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.6.6% of peers
• HTTP/3 advertisedHTTP/3 advertised.35% of peers
• Content Security Policy presentContent-Security-Policy present.37% of peers

What we saw

Homepage checked

https://www.oetker.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-17

CDN or edge

Google edge

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

570 KB, gzip

Images on homepage

78 (svg 3)

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 Food & Grocery Delivery sites

• checkers.co.za84
• cookpad.com84
• eatingonadime.com84
• sallysbakingaddiction.com84
• tastesbetterfromscratch.com84

Food & Grocery Delivery readiness benchmark