Skip to content
emailrules.today

Authentication history · 61 days observed

lufthansa.com

Observed from 4 Aug 2026 to 3 Oct 2026. 1 dated move on record, newest first.

Where it stands today

Live lookup, 3 Oct 2026. The same check /check/lufthansa.com runs.

  • 2fine
  • 2context

  • Looks fine

    present, ending -all

    Hard fail. The strictest setting and the right one once you are confident every sender is listed.

    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

    See what this looks like →

  • Looks fine

    present with p=reject

    A policy that actually instructs receivers, which is more than most senders publish.

    v=DMARC1; p=reject; fo=1; aspf=r; adkim=r; ri=3600; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:dmarc_agg@vali.email; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com

    From DMARC p=none is monitoring, not enforcementSee what this looks like →

  • Context

    No key found on the selectors we know

    This is inconclusive, not a failure. selectors cannot be listed from , so we probed the common ones for Klaviyo, Google, Microsoft, Mailchimp, SendGrid and Postmark. A custom selector will not show up here.

    From DKIM passing is not DKIM alignedSee what this looks like →

  • Context

    MX records present

    Where you receive mail says nothing about where you send it. Marketing sends usually leave through a different platform entirely.

    mxb-005f4701.gslb.pphosted.com, mxa-005f4701.gslb.pphosted.com

    See what this looks like →

What has moved

One entry per day a published record actually changed. Days we looked and found nothing different are counted, not listed.

  1. DMARC record changed.

    was: v=DMARC1; p=reject; fo=1; aspf=r; adkim=r; ri=3600; rua=mailto:lufthansa@rua.agari.com,mailto:dmarc_agg@vali.email; ruf=mailto:lufthansa@ruf.agari.com
now: v=DMARC1; p=reject; fo=1; aspf=r; adkim=r; ri=3600; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:dmarc_agg@vali.email; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com

    From DMARC p=none is monitoring, not enforcement

  2. First observation — what was already published

    SPF published.

    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

    DMARC published.

    v=DMARC1; p=reject; fo=1; aspf=r; adkim=r; ri=3600; rua=mailto:lufthansa@rua.agari.com,mailto:dmarc_agg@vali.email; ruf=mailto:lufthansa@ruf.agari.com

    No DKIM key on the selectors we probe.

    MX records present.

    mxa-005f4701.gslb.pphosted.com, mxb-005f4701.gslb.pphosted.com
Where this comes from. Public DNS, and nothing else. We read the same TXT and MX records any mail server reads before accepting a message, on the days someone looked. There is no scan, no login, no mail, and no score here — only what was published and the date we saw it. Gaps are days we did not get a clean answer from a resolver, and we would rather leave those blank than guess at them.
Run the full checkSee which rules are yours