Skip to content
emailrules.today

Authentication history · 61 days observed

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

  • 4fine
  • 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:spfip.asos.com include:spf.protection.outlook.com include:asos.gnatta.com include:em5214.asos.com include:mail.zendesk.com include:em9521.asos.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; rua=mailto:6904cc03@inbox.ondmarc.com,mailto:asos@rua.netcraft.com; ruf=mailto:6904cc03@inbox.ondmarc.com,mailto:asos@ruf.netcraft.com;

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

  • Looks fine

    keys published on 3 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), s2._domainkey (SendGrid), s1._domainkey (SendGrid)

    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=asos.com in the Authentication-Results header.

  • Looks fine

    SendGrid is authorised on notifications.asos.com

    SendGrid signs mail as this domain, and the root record does not name it — which on its own looks like a mismatch. It is not: notifications.asos.com publishes its own SPF naming SendGrid, and SPF is evaluated against the envelope domain rather than the root. This is the normal setup for bulk mail on a subdomain.

    v=spf1 include:spfip.asos.com include:spf.protection.outlook.com include:asos.gnatta.com include:em5214.asos.com include:mail.zendesk.com include:em9521.asos.com -all

    From Gmail enforces authentication, PTR, TLS and a 0.30 percent spam rateSee 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

    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.

    asos-com.mail.protection.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 include:spfip.asos.com include:spf.protection.outlook.com include:asos.gnatta.com include:em5214.asos.com include:mail.zendesk.com include:em9521.asos.com -all

    DMARC published.

    v=DMARC1; p=reject; rua=mailto:6904cc03@inbox.ondmarc.com,mailto:asos@rua.netcraft.com; ruf=mailto:6904cc03@inbox.ondmarc.com,mailto:asos@ruf.netcraft.com;

    DKIM keys on selectors we probe.

    s1._domainkey (SendGrid), s2._domainkey (SendGrid), selector1._domainkey (Microsoft 365)

    BIMI published.

    v=BIMI1; l=https://assets.asosservices.com/bimi/v2/asosw.svg; a=https://assets.asosservices.com/bimi/v2/asosw.pem;

    MX records present.

    asos-com.mail.protection.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