Skip to content
emailrules.today

Authentication history · 60 days observed

zalando.com

Observed from 4 Aug 2026 to 3 Oct 2026. Nothing published in DNS has moved in that window.

Where it stands today

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

  • 3fine
  • 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 include:_spf.google.com ip4:80.237.155.68 ip4:195.71.68.47 ip4:149.96.14.2 ip4:185.85.220.205 -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; rua=mailto:dmarc_rua@zalando.com; ruf=mailto:dmarc_ruf@zalando.com; adkim=s; pct=100;

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

  • Looks fine

    keys published on 1 selector

    A key existing is not the same as working. Read a real received header and check the d= value matches your before you call this done.

    google._domainkey (Google Workspace)

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

    Part platform, part you

    The key is your platform's to publish and it has. Whether it signs the domain in your is yours to confirm, and cannot show it — send one campaign to yourself and look for =pass header.d=zalando.com in the Authentication-Results header.

  • Context

    record published

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

    See what this looks like →

  • Context

    Receiving mail via Google Workspace

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

    smtp.google.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. First observation — what was already published

    SPF published.

    v=spf1 include:_spf.google.com ip4:80.237.155.68 ip4:195.71.68.47 ip4:149.96.14.2 ip4:185.85.220.205 -all

    DMARC published.

    v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@zalando.com; ruf=mailto:dmarc_ruf@zalando.com; adkim=s; pct=100;

    DKIM keys on selectors we probe.

    google._domainkey (Google Workspace)

    BIMI published.

    v=BIMI1;l=https://demand-cdn.s3.eu-central-1.amazonaws.com/tech-crm/BIMI/fs-V3/order_1503132189_logo.svg;a=https://demand-cdn.s3.eu-central-1.amazonaws.com/tech-crm/BIMI/fs-V3/zalando_se.pem

    MX records present.

    smtp.google.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