Skip to content
emailrules.today

Authentication history · 61 days observed

marksandspencer.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/marksandspencer.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 a:production.store.mns.demandware.net ip4:194.221.14.0/24 ip4:194.145.22.64 ip4:54.227.64.76 include:spf-0070d201.pphosted.com include:spf.protection.outlook.com include:authsmtp.com include:sendgrid.net -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; sp=reject; fo=1; pct=100; ri=3600; rua=mailto:marks-spencer@rua.agari-eu.com; ruf=mailto:marks-spencer@ruf.agari-eu.com

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

  • Looks fine

    keys published on 2 selectors

    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.

    selector1._domainkey (Microsoft 365), selector2._domainkey (Microsoft 365)

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

    Part platform, part you

    The key is SendGrid'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=marksandspencer.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 Microsoft 365

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

    marksandspencer-com.mail.eo.outlook.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 a:production.store.mns.demandware.net ip4:194.221.14.0/24 ip4:194.145.22.64 ip4:54.227.64.76 include:spf-0070d201.pphosted.com include:spf.protection.outlook.com include:authsmtp.com include:sendgrid.net -all

    DMARC published.

    v=DMARC1; p=reject; sp=reject; fo=1; pct=100; ri=3600; rua=mailto:marks-spencer@rua.agari-eu.com; ruf=mailto:marks-spencer@ruf.agari-eu.com

    DKIM keys on selectors we probe.

    selector1._domainkey (Microsoft 365), selector2._domainkey (Microsoft 365)

    BIMI published.

    v=BIMI1; l=https://d1asg2juabwvri.cloudfront.net/bimi_asset_40767fb1875f7d5dfe79e644142e2ed8.svg; a=https://d1asg2juabwvri.cloudfront.net/bimi_cert_bdb3033be0890744adbd952dc3080b68.pem

    MX records present.

    marksandspencer-com.mail.eo.outlook.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