lufthansa.com

Checked 5/14/2026, 10:53:04 PM · 52ms

Solid: p=reject is enforced.

DMARC record

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

Policy (p): reject
Subdomain policy (sp): inherits p=reject
Enforcement % (pct): 100%
DKIM alignment (adkim): r (relaxed)
SPF alignment (aspf): r (relaxed)
Aggregate reports (rua): mailto:[email protected], mailto:[email protected]
Failure reports (ruf): mailto:[email protected]

All tags (8)

vDMARC1DMARC version
prejectPolicy for the domain
fo1Failure reporting options
aspfr (relaxed)SPF alignment mode
adkimr (relaxed)DKIM alignment mode
ri3600Reporting interval (seconds)
ruamailto:[email protected],mailto:[email protected]Aggregate report URIs
rufmailto:[email protected]Forensic (failure) report URIs

SPF record

Found on the apex domain.

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

Recommendations

adkim=r (relaxed) is fine for most deployments. Consider adkim=s only if your DKIM signing matches the From: domain exactly.
aspf=r (relaxed) is fine for most deployments. Consider aspf=s only if your Return-Path aligns with the From: domain exactly.

AI-assisted remediation

Want a tailored fix plan in plain English?

Wiredepth Pro sends this report to our AI engine and streams back a 30-day rollout plan tailored to lufthansa.com, with provider-specific tips when we can infer them from the data. 10 playbooks per month on Pro, 100 on MSP.

ProSee Pro plans→

Check another domain

Or share this URL with the team that owns the records.