Skip to content
https://flightaware.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United States
308 Permanent Redirect
Checks
9
4 PASS 4 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2a06:98c1:3101::6812:25b3, 2a06:98c1:3104::ac40:964d
Info::
IPv6 connection error
Got: dial tcp6 [2a06:98c1:3101::6812:25b3]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2a06:98c1:3101::6812:25b3, 2a06:98c1:3104::ac40:964d Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 2349 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2349 B Sitemaps referenced 0 User-agents Download Ninja, WebReaper, Zao, SiteSnagger, HTTrack, ZyBORG, bingbot, Fetch, Teleport, linko, larbin, *, Applebot, DOC, Offline Explorer, NPBot, Cliqzbot, Irvine, Zealbot, MSIECrawler, Xenu, libwww, Twitterbot, UbiCrawler, WebCopier, TeleportPro, Microsoft.URL.Control, 360Spider, GPTBot, sitecheck.internetseer.com, WebStripper, grub-client, wget, WebZIP, k2spider Blocking No — crawling allowed
#
# robots.txt for www.flightaware.com hosted by itttt.dal.flightaware.com
#

#
# Specific unwanted clients
#

User-agent: UbiCrawler
Disallow: /

User-agent: DOC
Disallow: /

User-agent: Zao
Disallow: /

User-agent: sitecheck.internetseer.com
Disallow: /

User-agent: Zealbot
Disallow: /

User-agent: MSIECrawler
Disallow: /

User-agent: SiteSnagger
Disallow: /

User-agent: WebStripper
Disallow: /

User-agent: WebCopier
Disallow: /

User-agent: Fetch
Disallow: /

User-agent: Offline Explorer
Disallow: /

User-agent: Teleport
Disallow: /

User-agent: TeleportPro
Disallow: /

User-agent: WebZIP
Disallow: /

User-agent: linko
Disallow: /

User-agent: HTTrack
Disallow: /

User-agent: Microsoft.URL.Control
Disallow: /

User-agent: Xenu
Disallow: /

User-agent: larbin
Disallow: /

User-agent: libwww
Disallow: /

User-agent: ZyBORG
Disallow: /

User-agent: Download Ninja
Disallow: /

User-agent: grub-client
Disallow: /

User-agent: k2spider
Disallow: /

User-agent: NPBot
Disallow: /

User-agent: WebReaper
Disallow: /

User-agent: Irvine
Disallow: /

User-agent: 360Spider
Disallow: /

User-agent: bingbot
Crawl-delay: 1

#
# Command line recursive requests as well as automated fetching from the non-
# exportable data is not acceptable.
#
# See:
#	https://www.flightaware.com/about/termsofuse
#	https://www.flightaware.com/commercial/flightxml/
#
User-agent: wget
Disallow: /account/
Disallow: /analysis/
Disallow: /include/
Disallow: /live/
Disallow: /resources/
Disallow: /map/
Disallow: /me/
Disallow: /photos/


#
# General robot rules
#
User-agent: *
Disallow: /account/
Disallow: /ajax/
Disallow: /bait/
Disallow: /errors/
Disallow: /live/flight/id/
Disallow: /mapi/
Disallow: /me/
Disallow: /photos/upload.rvt
Disallow: /photos/upload
Disallow: /mp/
Disallow: /live/report.rvt
Disallow: /adsb/register
Disallow: /adsb/request
Disallow: /adsb/flightfeeder/terms
Disallow: /photos/crowdsource/
Disallow: /photos/crowdsource.rvt
Disallow: /commercial/flightxml/v3/

#
# Stop Applebot from beating the crap out of ajax endpoints (specifically the
# static flight map one)
#
User-agent: Applebot
Disallow: /ajax/

User-agent: Cliqzbot
Disallow: /

# Allow Twitter to grab article and careers blobs
User-agent: Twitterbot
Allow: /news/
Allow: /about/careers/

# Stop OpenAI/ChatGPT from training on our data
User-agent: GPTBot
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.flightaware.com/
200https://flightaware.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://flightaware.com/ https://www.flightaware.com/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

77
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
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f074788bc176037-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f074788bc176037-SJC
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.37.179, 172.64.150.77
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3101::6812:25b3, 2a06:98c1:3104::ac40:964d
Info::
2 nameserver(s) configured
Got: ns0014.secondary.cloudflare.com, ns0218.secondary.cloudflare.com
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: 9 ms
Got: 9 ms
A104.18.37.179, 172.64.150.77
AAAA2a06:98c1:3101::6812:25b3, 2a06:98c1:3104::ac40:964d
CNAME
NSns0014.secondary.cloudflare.com, ns0218.secondary.cloudflare.com
MX
10 mxa-00105402.gslb.gpphosted.com
10 mxb-00105402.gslb.gpphosted.com
TXT
MS=ms60664667
ZOOM_verify_Qa17wLTjQ_OeaStsqWv0Hw
apple-domain-verification=fa6k7RseRZcEks32
atlassian-domain-verification=F/rTqK1hCh5HdlNP/z25uOQ3ixzkIDdqiZOww80TNEUUZzAJi8...
facebook-domain-verification=08bfp7bw29hrab635knqithq52m8km
google-site-verification=JbCfXxZGmBwjVmiAOO2UBCgv4M3vc6qAOHTNqkjyyDU
google-site-verification=RJy4o7_w1bK1ONwszHQVESt3QlU6O7ZAhyuvfmyCrc4
google-site-verification=pzE4BEPMB9wQhpIl2Wiea8uL60VWQs_z-X_8nHDXqYY
intacct-esk=549E9B0F04067230E0538C06A8C040FD
keybase-site-verification=Fay6NCK8ApMxT10Dn1WeVMkdc4VBiuSNgMaX9e9Veuc
onetrust-domain-verification=864cc49af2d642b0a260c06c5a557c2d
smartsheet-site-validation=auqkPcmu2H-bAG3IyeOBM2AW_GGYuZ4_
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
wiz-domain-verification=0e15001f32475978c40d426288e19f1d7862699bf1a5ff045dfca280...
CAALookup not available with standard resolver
Resolved in 9 ms

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
Redirect Chain
1 redirect(s), 144 ms total
PASS
1 redirect(s), 144 ms total
Info::
Single redirect
Got: https://flightaware.com → https://www.flightaware.com/ (308)
Info::
WWW normalization redirect

https://flightaware.com

30 ms · HTTP/1.1

308

https://www.flightaware.com/

114 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://flightaware.com30830 msHTTP/1.1cloudflare
2https://www.flightaware.com/200114 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
flightaware.com — via Domain.com - Network Solutions, LLC, 21 years, 4 months old, hosted on Cloudflare
PASS
flightaware.com — via Domain.com - Network Solutions, LLC, 21 years, 4 months old, hosted on Cloudflare
Info::
Domain registered until Mar 18, 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: Domain.com - Network Solutions, LLC
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: Cloudflare
Got: AS13335
Domain expiry

275 days

March 18, 2027

SSL certificate

77 days

Issued by Google Trust Services

Domain age

21 years, 4 months

Registered March 18, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.37.179

Registrar

Domain.com - Network Solutions, LLC

Unlocked 2 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 Domain.com - Network Solutions, LLC
Created March 18, 2005 (21 years, 4 months ago)
Expires March 18, 2027 (10 months)
Last Updated February 26, 2026
Name Servers evan.ns.cloudflare.com, samara.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.18.37.179
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.1s)

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 28 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
5 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
12 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
29 ms
Total Time Total request time from DNS lookup through full response.
29 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 5 ms TLS Handshake 12 ms Server Processing 6 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