airindiaexpress.com

Readiness by lane

Green: airindiaexpress.com. Thin bar: Airlines peer median.

Priority fixes for airindiaexpress.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

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

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   32% of Airlines peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

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

   16% of Airlines peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for airindiaexpress.com, 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.9% of Airlines peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What airindiaexpress.com already does well

Practices fewer than half of Airlines peers use.

• Nameservers spread across providersNameservers spread across more than one operator.19% of peers
• Referrer-Policy setReferrer-Policy present.25% of peers
• Reachable over IPv6IPv6 address published.35% of peers

What we saw

Homepage checked

https://www.airindiaexpress.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Akamai

Platform or framework

Adobe Experience Manager

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

9 KB, gzip

Images on homepage

0

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

• airbaltic.com81
• akasaair.com81
• copaair.com79
• finnair.com79
• ryanair.com81

Airlines readiness benchmark