Skip to content
emailrules.today

Authentication history · 59 days observed

ryanair.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/ryanair.com runs.

  • 2fine
  • 3context

  • Looks fine

    present, ending ~all

    Soft fail. Accepted everywhere, though -all is stronger once your sender list is complete.

    v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~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; rua=mailto:dmarc_agg@vali.email

    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

    record published

    Your logo can appear in supporting clients, which needs at quarantine or reject.

    See 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.

    de-smtp-inbound-1.mimecast.com, de-smtp-inbound-2.mimecast.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. BIMI record changed.

    was: v=BIMI1; l=https://amplify.valimail.com/bimi/ryanair/JgDx5m5g7Bx-ryanair_dac_1323452655.svg; a=https://amplify.valimail.com/bimi/ryanair/JgDx5m5g7Bx-ryanair_dac_1323452655.pem
now: v=BIMI1; l=https://amplify.valimail.com/bimi/ryanair/7q-cXh-F-Pe-ryanair_dac_1578712082.svg; a=https://amplify.valimail.com/bimi/ryanair/7q-cXh-F-Pe-ryanair_dac_1578712082.pem

    From BIMI shows a logo after DMARC — it is not a bulk-sender mandate

  2. First observation — what was already published

    SPF published.

    v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all

    DMARC published.

    v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email

    No DKIM key on the selectors we probe.

    BIMI published.

    v=BIMI1; l=https://amplify.valimail.com/bimi/ryanair/JgDx5m5g7Bx-ryanair_dac_1323452655.svg; a=https://amplify.valimail.com/bimi/ryanair/JgDx5m5g7Bx-ryanair_dac_1323452655.pem

    MX records present.

    de-smtp-inbound-1.mimecast.com, de-smtp-inbound-2.mimecast.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