Nothing here is yours.
One finding is shared with Mailchimp. The mechanical half is done and the judgement is still yours.
19 DNS lookups23 blocklists askedno entriesno score, ever
read from DNS, quoted verbatim
- SPF
- ~all
- DMARC
- p=reject
- DKIM
- 4 selectors
- BIMI
- optional
- MX
- Google Workspace
- LISTS
- 23 asked
Who sends as you
3 Oct 2026 · no score, no grade, nothing inferred
Who this domain authorises
You send through Mailchimp
- include:servers.mcsv.netread from your SPF, verbatim
- k1._domainkeyDKIM key present
You send through SendGrid
- include:u1369857.wl.sendgrid.netread from your SPF, verbatim
- s1._domainkeyDKIM key present
- s2._domainkeyDKIM key present
Your SPF authorises Amazon SES
- include:amazonses.comread from your SPF, verbatim
include:_spf.salesforce.com · google._domainkey is Salesforce and Google Workspace, 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, which is why an include on its own is reported as permission rather than as use. Only a real message names the address that actually sent your campaign.
Whose job each one is
- 3fine
- 1context
Looks fine
present, ending ~all
Soft fail. Accepted everywhere, though -all is stronger once your sender list is complete.
v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com include:_spf.salesforce.com include:u1369857.wl.sendgrid.net include:mg-spf.greenhouse.io include:servers.mcsv.net include:amazonses.com a:mcsrel.hopexcloud.com ip4:167.89.0.0/17 ip4:168.245.0.0/17 ~all
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:e8c3477c8426723@rep.dmarcanalyzer.com,mailto:n26@rua.netcraft.com; ruf=mailto:e8c3477c8426723@for.dmarcanalyzer.com,mailto:n26@ruf.netcraft.com; pct=100; sp=reject; fo=1; adkim=r; aspf=r;
From DMARC p=none is monitoring, not enforcementSee what this looks like →
Looks fine
keys published on 4 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.
google._domainkey (Google Workspace), k1._domainkey (Mailchimp), s2._domainkey (SendGrid), s1._domainkey (SendGrid)
From DKIM passing is not DKIM alignedSee what this looks like →
Part platform, part you
The key is Mailchimp'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=n26.com in the Authentication-Results header.
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.
aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com
Blocklists
Nothing has an entry for you.
23 lists asked0 with an entry1 could not be asked
n26.com is not on any of the 23 lists that answered us today. That is the whole result — there is no score, and a clean answer is allowed to be short.
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
- URIBLanswered
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 n26.com actually changes. Same list as rule alerts — one inbox, one promise.