Skip to content
https://aircanada.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
B
Redirect Chain
2 redirect(s), 546 ms total
REVIEW
2 redirect(s), 546 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Redirect overhead: 546 ms total
Got: 546 ms

https://aircanada.com

18 ms · HTTP/1.1

301

https://aircanada.com/home/es/es/aco/fli...

18 ms · HTTP/1.1

301

https://www.aircanada.com/home/es/es/aco...

510 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://aircanada.com30118 msHTTP/1.1AkamaiGHost
2https://aircanada.com/home/es/es/aco/fli...30118 msHTTP/1.1AkamaiGHost
3https://www.aircanada.com/home/es/es/aco...200510 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
162 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

162
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 36 ms lookup
PASS
1 A records, 36 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 2.22.209.246
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a20-67.akam.net, a12-66.akam.net, a8-65.akam.net, a1-4.akam.net, a11-65.akam.net, a3-64.akam.net
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 36 ms
Got: 36 ms
A2.22.209.246
AAAA
CNAME
NSa20-67.akam.net, a12-66.akam.net, a8-65.akam.net, a1-4.akam.net, a11-65.akam.net, a3-64.akam.net
MX
10 30849360.in1.mandrillapp.com
20 30849360.in2.mandrillapp.com
TXT
if4jonuej7p1f624hhjj8i8mvb
facebook-domain-verification=qdit6bufa56nas6nf2g4blgxc5mc7v
_sd3pejak45dbafpaya9dlws4rioqfpv
pardot538133=dfe8e409913242af4bcac56dc70cca85992832f4a0bf17290ab4ea04068f1aac
pardot1014382=1a60e433e83cee62786f3032a4b9a1cf77b5cb80126d47a33a6a23e24a15053f
2l49m6wpnp1z9f73wjdxvwjgd2ncc79c
sending_domain538133=62f5b847cc172bccab52fb7b2c05f57babd358b9a567acba758e3da1adf...
sending_domain1014382=143d620760db9354f5f4c78a2d303561d7f45b21e8a76b85c8c9cd1446...
SPF v=spf1 include:mailgun.org include:spf.mandrillapp.com include:spf.protection.ou...
CAALookup not available with standard resolver
Resolved in 36 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.aircanada.com/
200https://aircanada.com/

Preferred variant: non-www

HTTP → HTTPS

301http://aircanada.com/ https://aircanada.com/home/es/es/aco/flights

Consistent

A+
Domain Intelligence
aircanada.com — via CSC Corporate Domains, Inc., 25 years, 6 months old, hosted on Akamai
PASS
aircanada.com — via CSC Corporate Domains, Inc., 25 years, 6 months old, hosted on Akamai
Info::
Domain registered until Feb 14, 2027 (10 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Akamai
Got: AS16625
Domain expiry

216 days

February 14, 2027

SSL certificate

162 days

Issued by COMODO CA Limited

Domain age

25 years, 6 months

Registered February 14, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

2.22.209.246

Registrar

CSC Corporate Domains, Inc.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created February 14, 2001 (25 years, 6 months ago)
Expires February 14, 2027 (10 months)
Last Updated February 10, 2026
Name Servers a1-4.akam.net, a11-65.akam.net, a12-66.akam.net, a20-67.akam.net, a3-64.akam.net, a8-65.akam.net
DNSSEC Not enabled
Hosting
IP Address 2.22.209.246
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 65 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
65 ms
Total Time Total request time from DNS lookup through full response.
65 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 25 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback