alaskaair.com

Readiness by lane

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

Priority fixes for alaskaair.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 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   45% of Airlines peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

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

   On Next.js: Add it in next.config.js headers().

   60% of Airlines peers do this.

   Guide: A Practical Website Health Check for 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.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   32% of Airlines peers do this.

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

What alaskaair.com already does well

Practices fewer than half of Airlines peers use.

• Static files cached for 30 days or moreLong-lived caching on static files.40% of peers

What we saw

Homepage checked

https://www.alaskaair.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Entrust Limited, 396-day validity, expiring 2027-01-31

CDN or edge

Fastly, Azure Front Door/CDN

Platform or framework

Next.js, Sitecore

DNS operators

Vercara UltraDNS

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

3,107 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

• aircanada.com56
• ar-svx.ru55
• delta.com58
• philippineairlines.com58
• westjet.com58

Airlines readiness benchmark