Nothing here needs you.
19 DNS lookups22 blocklists asked1 with an entryno score, ever
read from DNS, quoted verbatim
- SPF
- -all
- DMARC
- p=quarantine
- DKIM
- inconclusive
- BIMI
- optional
- MX
- receiving
- LISTS
- 22 asked
3 Oct 2026 · no score, no grade, nothing inferred
Who this domain authorises
Your sender list is held by Proofpoint
include:spf-00921b02.pphosted.com
The senders sit behind that one include and are managed there rather than published here. Whoever administers Proofpoint holds the answer to which platforms may send as you; this page can only report what your own record says.
include:_spf.salesforce.com is Salesforce, which is where staff read mail. It says nothing about where campaigns leave from, and a checker that counts it as your sending platform has told you about your inbox, not your list.
This is what your DNS authorises, not proof of what you send. A domain can authorise a platform it stopped paying for two years ago. Only a real message names the address that actually sent your campaign.
Whose job each one is
- 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
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
Blocklists
Nothing here needs you. One entry looks alarming and is not about you.
22 lists asked1 with an entry2 could not be asked
Ignore this
UCEPROTECT Level 3has 50.31.53.62
Entire autonomous systems — every address a provider announces. An entry here is a statement about your provider, not about you.
Who can remove it →127.0.0.2
Every other checker we know of shows the entries above in the same red as the ones that matter. That is how a marketer ends up paying somebody to remove a listing that was never about them.
Which lists, and which would not answer
- SpamCopanswered
- PSBLanswered
- Mailspikeanswered
- Spam Eating Monkeyanswered
- blocklist.deanswered
- 0SPAManswered
- InterServeranswered
- SPFBLdid not confirm the entry it is required to publish
- GBUdb Truncateanswered
- s5h.netanswered
- ZapBLanswered
- SWINOGanswered
- Kemptanswered
- Anonmailsanswered
- Fabelanswered
- NoSolicitadoanswered
- Schulteanswered
- JIPPGanswered
- UCEPROTECT Level 1answered
- UCEPROTECT Level 2answered
- UCEPROTECT Level 3answered
- Backscattereranswered
- SEM Backscatteranswered
- URIBLdeclined the query
Each of these answered an entry it is required to publish, and one it is required not to, before we believed anything it said about you. A list that fails either is reported as unanswered rather than as clean — because a blocklist that declines to reply looks exactly like one giving you the all-clear. How we choose them.
We have observed this domain on 61 days. See what has moved since.
Putting this in a client report? Embed a live, dated badge that re-checks itself.
Watch this domain
One email if authentication DNS for johnlewis.com actually changes. Same list as rule alerts — one inbox, one promise.