reisereporter.de

Readiness by lane

Green: reisereporter.de. Thin bar: Travel Bookings & Trip Planning peer median.

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

   46% of Travel Bookings & Trip Planning 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

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   83% of Travel Bookings & Trip Planning peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for reisereporter.de was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   50% of Travel Bookings & Trip Planning peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   56% of Travel Bookings & Trip Planning peers do this.

   Guide: A Practical Website Health Check for Owners

What reisereporter.de already does well

Practices fewer than half of Travel Bookings & Trip Planning peers use.

• Nameservers spread across providersNameservers spread across more than one operator.13% of peers
• security.txt publishedsecurity.txt with a contact found.17% of peers
• Content Security Policy presentContent-Security-Policy present.30% of peers

What we saw

Homepage checked

https://www.reisereporter.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

DNS operators

3 self-run or other nameserver domains

DMARC policy

p=none

Homepage HTML

470 KB, gzip

Images on homepage

65 (jpg 453, png 20, webp 16, gif 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

Compare with other Travel Bookings & Trip Planning sites

• maxmilhas.com.br73
• ncl.com73
• pelago.com73
• traum-ferienwohnungen.de73
• trip.com73

Travel Bookings & Trip Planning readiness benchmark