Skip to content
https://www.lufthansa.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from New York, United Stated
403 Forbidden
Checks
9
5 PASS 4 REVIEW
B
DNS Records
2 A records, 21 ms lookup
REVIEW
2 A records, 21 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.8.228, 104.18.9.228
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:8e4, 2606:4700::6812:9e4
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.lufthansa.com.cdn.cloudflare.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 21 ms
Got: 21 ms
A104.18.8.228, 104.18.9.228
AAAA2606:4700::6812:8e4, 2606:4700::6812:9e4
CNAMEwww.lufthansa.com.cdn.cloudflare.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 21 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 242 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 242 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
# robots.txt https://www.lufthansa.com/

User-agent: *
Allow: /
Disallow: /deeplink
Disallow: /service/secured

Sitemap: https://www.lufthansa.com/sitemap/sitemap_lh.xml.gz
Sitemap: https://www.lufthansa.com/aircore/sitemaps/sitemap-index.xml
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
187 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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: EWR)
Got: cf-ray: 9e8bdbde7fefa4a0-EWR
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8bdbde7fefa4a0-EWR
A
Redirect Chain
1 redirect(s), 176 ms total
PASS
1 redirect(s), 176 ms total
Info::
Single redirect
Got: https://www.lufthansa.com → https://www.lufthansa.com/us/en/homepage (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.lufthansa.com

https://www.lufthansa.com

134 ms · HTTP/1.1

302

https://www.lufthansa.com/us/en/homepage

42 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.lufthansa.com302134 msHTTP/1.1cloudflare
2https://www.lufthansa.com/us/en/homepage20042 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:8e4, 2606:4700::6812:9e4
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:8e4, 2606:4700::6812:9e4 Connection Reachable (1 ms)
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: www

HTTP → HTTPS

301http://www.lufthansa.com/ https://www.lufthansa.com/

Consistent

A+
Domain Intelligence
lufthansa.com — via CSC Corporate Domains, Inc., 30 years, 8 months old, hosted on Microsoft Azure
PASS
lufthansa.com — via CSC Corporate Domains, Inc., 30 years, 8 months old, hosted on Microsoft Azure
Info::
Domain registered until Jan 9, 2027 (9 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: CSC Corporate Domains, Inc.
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

180 days

January 9, 2027

SSL certificate

187 days

Issued by Sectigo Limited

Domain age

30 years, 8 months

Registered January 10, 1996

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

20.101.251.232

Registrar

CSC Corporate Domains, Inc.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar CSC Corporate Domains, Inc.
Created January 10, 1996 (30 years, 8 months ago)
Expires January 9, 2027 (9 months)
Last Updated January 5, 2026
Name Servers udns1.cscudns.com, udns2.cscudns.org
DNSSEC Enabled
Hosting
IP Address 20.101.251.232
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.1s)
A+
HTTP Probe Timing
Total 33 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.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
33 ms
Total Time Total request time from DNS lookup through full response.
33 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 2 ms TLS Handshake 10 ms Server Processing 16 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