Skip to content
emailrules.today

Authentication history · 61 days observed

johnlewis.com

Observed from 4 Aug 2026 to 3 Oct 2026. 2 dated moves on record, newest first.

Where it stands today

Live lookup, 3 Oct 2026. The same check /check/johnlewis.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 ip4:193.35.248.0/21 ip4:212.117.224.200/29 ip4:195.11.6.128 ip4:50.31.53.62 ip4:62.73.158.39/32 ip4:62.73.158.40/32 include:spf-00921b02.pphosted.com include:_spf.salesforce.com include:rnmk.com include:email-od.com include:gateways.firstdata.com include:spf-00921b01.pphosted.com -all

    See what this looks like →

  • Looks fine

    present with p=quarantine

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

    v=DMARC1; p=quarantine; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com,mailto:dmarc-ruf@dmarc-johnlewis.co.uk; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:dmarc-rua@dmarc-johnlewis.co.uk

    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-00921b02.gslb.pphosted.com, mxa-00921b02.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. SPF record changed.

    was: v=spf1 ip4:193.35.248.0/21 ip4:212.117.224.200/29 ip4:195.11.6.128 ip4:50.31.53.62 ip4:62.73.158.39/32 ip4:62.73.158.40/32 include:spf-00921b02.pphosted.com include:_spf.salesforce.com include:rnmk.com include:email-od.com include:gateways.firstdata.com -all
now: v=spf1 ip4:193.35.248.0/21 ip4:212.117.224.200/29 ip4:195.11.6.128 ip4:50.31.53.62 ip4:62.73.158.39/32 ip4:62.73.158.40/32 include:spf-00921b02.pphosted.com include:_spf.salesforce.com include:rnmk.com include:email-od.com include:gateways.firstdata.com include:spf-00921b01.pphosted.com -all

    From Gmail enforces authentication, PTR, TLS and a 0.30 percent spam rate

  2. MX hosts changed.

    was: js-relay1.johnlewis.co.uk, js-relay11.johnlewis.co.uk, js-relay15.johnlewis.co.uk, js-relay17.johnlewis.co.uk, js-relay3.johnlewis.co.uk, js-relay5.johnlewis.co.uk, js-relay7.johnlewis.co.uk, js-relay9.johnlewis.co.uk, ws-relay1.johnlewis.co.uk, ws-relay11.johnlewis.co.uk, ws-relay15.johnlewis.co.uk, ws-relay17.johnlewis.co.uk, ws-relay3.johnlewis.co.uk, ws-relay5.johnlewis.co.uk, ws-relay7.johnlewis.co.uk, ws-relay9.johnlewis.co.uk
now: mxa-00921b02.gslb.pphosted.com, mxb-00921b02.gslb.pphosted.com

  3. First observation — what was already published

    SPF published.

    v=spf1 ip4:193.35.248.0/21 ip4:212.117.224.200/29 ip4:195.11.6.128 ip4:50.31.53.62 ip4:62.73.158.39/32 ip4:62.73.158.40/32 include:spf-00921b02.pphosted.com include:_spf.salesforce.com include:rnmk.com include:email-od.com include:gateways.firstdata.com -all

    DMARC published.

    v=DMARC1; p=quarantine; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com,mailto:dmarc-ruf@dmarc-johnlewis.co.uk; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:dmarc-rua@dmarc-johnlewis.co.uk

    No DKIM key on the selectors we probe.

    MX records present.

    js-relay1.johnlewis.co.uk, js-relay11.johnlewis.co.uk, js-relay15.johnlewis.co.uk, js-relay17.johnlewis.co.uk, js-relay3.johnlewis.co.uk, js-relay5.johnlewis.co.uk, js-relay7.johnlewis.co.uk, js-relay9.johnlewis.co.uk, ws-relay1.johnlewis.co.uk, ws-relay11.johnlewis.co.uk, ws-relay15.johnlewis.co.uk, ws-relay17.johnlewis.co.uk, ws-relay3.johnlewis.co.uk, ws-relay5.johnlewis.co.uk, ws-relay7.johnlewis.co.uk, ws-relay9.johnlewis.co.uk
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