ethiopianairlines.com

Readiness by lane

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

Priority fixes for ethiopianairlines.com

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   91% of Airlines peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

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

   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.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 6 hours, 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 · 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

What ethiopianairlines.com already does well

Practices fewer than half of Airlines peers use.

• Referrer-Policy setReferrer-Policy present.25% of peers
• Structured data presentJSON-LD structured data found.30% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.45% of peers

What we saw

Homepage checked

https://www.ethiopianairlines.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2026-12-02

CDN or edge

Akamai

DNS operators

GoDaddy DNS

HSTS

max-age 30 days

DMARC policy

p=reject

Homepage HTML

21 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

• airalgerie.dz64
• airarabia.com65
• condor.com65
• flightaware.com66
• solaseedair.jp64

Airlines readiness benchmark