Dataweaz

lufthansa.com

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
January 10, 1996
Expires on
January 9, 2027
Name servers
udns1.cscudns.com, udns2.cscudns.org
Mail servers
mxb-005f4701.gslb.pphosted.com, mxa-005f4701.gslb.pphosted.com
DMARC
Reject
DKIM
No key found among the common selectors

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from lufthansa.com but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Failure reports
[email protected]

Record

v=DMARC1; p=reject; fo=1; aspf=r; adkim=r; ri=3600; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for lufthansa.com.

RuleValueResult
mx—Allowed
ip4129.35.195.69Allowed
ip4129.35.195.68Allowed
ip4129.35.195.132Allowed
ip4129.35.195.133Allowed
ip484.17.165.165Allowed
ip484.17.165.167Allowed
ip4194.31.6.64/28Allowed
ip452.157.235.82Allowed
ip480.72.142.246Allowed
ip480.77.215.176/28Allowed
ip484.17.184.240/28Allowed
ip484.17.190.192/26Allowed
includespf.ecentry.ioAllowed
includeamazonses.comAllowed
include_relay.amadeus.comAllowed
include_spf.lufthansa.comAllowed
all—Rejected

Top-level DNS lookups: 5 of 10 allowed

Record

v=spf1 mx ip4:129.35.195.69 ip4:129.35.195.68 ip4:129.35.195.132 ip4:129.35.195.133 ip4:84.17.165.165 ip4:84.17.165.167 ip4:194.31.6.64/28 ip4:52.157.235.82 ip4:80.72.142.246 ip4:80.77.215.176/28 ip4:84.17.184.240/28 ip4:84.17.190.192/26 include:spf.ecentry.io include:amazonses.com include:_relay.amadeus.com include:_spf.lufthansa.com -all

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to lufthansa.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from lufthansa.com was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @lufthansa.com address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

lufthansa.com  MX  10 mx1.lufthansa.com.
lufthansa.com  MX  20 mx2.lufthansa.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.lufthansa.com.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

lufthansa.com  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.lufthansa.com, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.lufthansa.com  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.lufthansa.com, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.lufthansa.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of lufthansa.com

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

TypeIP address
A20.101.251.232

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
udns1.cscudns.com204.74.66.14
udns2.cscudns.org204.74.104.20

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @lufthansa.com addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
10mxb-005f4701.gslb.pphosted.com66.159.233.224
10mxa-005f4701.gslb.pphosted.com143.55.150.105

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.lufthansa.com.

NameContent
lufthansa.comv=spf1 mx ip4:129.35.195.69 ip4:129.35.195.68 ip4:129.35.195.132 ip4:129.35.195.133 ip4:84.17.165.165 ip4:84.17.165.167 ip4:194.31.6.64/28 ip4:52.157.235.82 ip4:80.72.142.246 ip4:80.77.215.176/28 ip4:84.17.184.240/28 ip4:84.17.190.192/26 include:spf.ecentry.io include:amazonses.com include:_relay.amadeus.com include:_spf.lufthansa.com -all
lufthansa.comfacebook-domain-verification=jr9ai9g9jfp6b646oq7kay8xw4edgp
lufthansa.comapple-domain-verification=dgPxFEVd2K3xQqtz
lufthansa.comgoogle-site-verification=F9d17-cGR9pWXhdWBAAoVSCULdLFHg581R98t75oZ9M
lufthansa.comdocusign=8bea4f11-e5ab-4856-99e4-4ca3d798adaf
lufthansa.comgoogle-site-verification=A1d4RptY5Tgo2iMXRQUdNN1YDiCDRF9qi8rogpch4hQ
lufthansa.com1qbYXTIQfi1P3mqgJMun2NUm9qbzeAmMCvRn0q+p3wNof6cn0F3+vN3JHmLIkyAuA8yz1ya0IKosGsOs8Npt/Q==
lufthansa.com_3lqbnk5ht5r15umni1kxyppvmdy3y1c
lufthansa.comatlassian-domain-verification=xYk1MY7WWFEakmSsrr5YC8zYGHTK1S8RFowd0HChxOpoFSnbf9YMRruJegIt4EMG
lufthansa.comcloudpiercer-verification=dc4279b6fad885058db091939393c054
lufthansa.comslido-domain-verification=345a9c65-9fa3-4518-a7fe-248ee2a7b644
lufthansa.comqucYgggiw9JwlYkwN1eWMmo+t5nlajTRSugGKykCY1g0BBFD5fa+U3YYCGL2jDR0c4T1gQD02IZyJsUEYMmTkA==
lufthansa.com ir0llfualq0lc0rrpus8hckeir
lufthansa.comMS=ms85757355
lufthansa.com_atv5tb360u8dld1ndsus1qfru3cf6pt
lufthansa.com_rd9relssqtk8z4vl6yn9hk66l4fc8zd
lufthansa.comcloudControl-verification: f6b65ab213e089875abd83bd4220d316ad10b16e4e64e2ccabef24e86eb3b563
lufthansa.com_globalsign-domain-verification=VzENNhYl3dL1bbkkax4Zn0AKFBSeyIt9K3GSm43box
_dmarc.lufthansa.comv=DMARC1; p=reject; fo=1; aspf=r; adkim=r; ri=3600; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]

Related IP addresses

IPv4 addresses used by lufthansa.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
20.101.251.232Website20.101.251.0/24
204.74.66.14Name server udns1.cscudns.com204.74.66.0/24
204.74.104.20Name server udns2.cscudns.org204.74.104.0/24
66.159.233.224Mail server mxb-005f4701.gslb.pphosted.com66.159.233.0/24
143.55.150.105Mail server mxa-005f4701.gslb.pphosted.com143.55.150.0/24
129.35.195.69Authorized by SPF129.35.195.0/24
129.35.195.68Authorized by SPF129.35.195.0/24
129.35.195.132Authorized by SPF129.35.195.0/24
129.35.195.133Authorized by SPF129.35.195.0/24
84.17.165.165Authorized by SPF84.17.165.0/24
84.17.165.167Authorized by SPF84.17.165.0/24
52.157.235.82Authorized by SPF52.157.235.0/24
80.72.142.246Authorized by SPF80.72.142.0/24

WHOIS of the domain lufthansa.com

Domain Name: LUFTHANSA.COM
   Registry Domain ID: 5443874_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2026-01-05T06:07:01Z
   Creation Date: 1996-01-10T05:00:00Z
   Registry Expiry Date: 2027-01-09T05:00:00Z
   Registrar: CSC Corporate Domains, Inc.
   Registrar IANA ID: 299
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: 8887802723
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: UDNS1.CSCUDNS.COM
   Name Server: UDNS2.CSCUDNS.ORG
   DNSSEC: signedDelegation
   DNSSEC DS Data: 14242 13 1 9B66EB062C699AA11230E337EEAF8244050A2274
   DNSSEC DS Data: 14242 13 2 493A0CDD768647DBE5F7F48BD070AC739056B62729A384BBA934320438280A0A
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T21:37:28Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.