frankfurt-airport.com

Readiness by lane

Green: frankfurt-airport.com. Thin bar: Airlines peer median.

Priority fixes for frankfurt-airport.com

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 1 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.

   60% of Airlines 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

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.frankfurt-airport.com.

   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.

   63% of Airlines peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 600 seconds, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   40% of Airlines peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 11 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.

   31% of Airlines peers do this.

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

What frankfurt-airport.com already does well

Practices fewer than half of Airlines peers use.

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

What we saw

Homepage checked

https://www.frankfurt-airport.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Entrust Limited, 396-day validity, expiring 2027-04-04

Platform or framework

Adobe Experience Manager

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 1 days

Homepage HTML

194 KB, gzip

Images on homepage

11 (jpg 10, png 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 Airlines sites

• airalgerie.dz64
• solaseedair.jp64
• virginatlantic.com64
• vivaaerobus.com63
• volaris.com63

Airlines readiness benchmark