myheritage.de

Readiness by lane

Green: myheritage.de. Thin bar: Family & Heritage peer median.

Priority fixes for myheritage.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 30 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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   43% of Family & Heritage 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.

   67% of Family & Heritage peers do this.

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

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 6 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   25% of Family & Heritage peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

   31% of Family & Heritage peers do this.

   Guide: CDN Guide for Website Owners

What myheritage.de already does well

Practices fewer than half of Family & Heritage peers use.

• CAA records limit who can issue certificatesCAA limits issuance to www.digicert.com.28% of peers
• Content Security Policy presentContent-Security-Policy present.34% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked

https://www.myheritage.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 130-day validity, expiring 2026-11-12

CDN or edge

Amazon CloudFront, Imperva

DNS operators

NS1

HSTS

max-age 30 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

194 KB, gzip

Images on homepage

6 (png 12, svg 1, gif 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

Compare with other Family & Heritage sites

• hommages.ch72
• libramemoria.com71
• myheritage.com71
• myheritage.es71
• myheritage.fr71

Family & Heritage readiness benchmark