zapier.com
Authenticated end to end and enforced. Spoofed mail is rejected outright.
7 of 8 checks pass · 8 tools visible in DNS · nothing urgent
1 · Authentication and transport
SPF
PassValid, hard failAnything not on the list is rejected. The strongest setting.
v=spf1 include:_spf.google.com include:mailgun.org include:7462085.spf03.hubspotemail.net include:mail.zendesk.com include:_spf.qualtrics.com -all
DKIM
Pass6 keys foundSelectors google, s1, s2, smtp, mandrill, pm publish a public key. 2 of them point at a vendor by CNAME.
google._domainkey, s1._domainkey, s2._domainkey, smtp._domainkey, mandrill._domainkey, pm._domainkey
DMARC
PassEnforced (p=reject)Failing mail is rejected. This is the finish line.
v=DMARC1; p=reject; pct=100; rua=mailto:re+imuzho2gzgl@dmarc.postmarkapp.com,mailto:dmarc_agg@dmarc.everest.email; ruf=mailto:dmarc_fr@dmarc.everest.email; sp=reject; aspf=r; adkim=r;
MX
Pass7 hostsMore than one receiving server, so a single outage does not bounce mail.
10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 alt3.aspmx.l.google.com 50 alt4.aspmx.l.google.com 60 ms74255568.msv1.invalid 70 noreply.qemailserver.com
MTA-STS
PassPublishedThe DNS record is present. The policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt cannot be read from a browser, so its mode is not verified here.
v=STSv1;id=1585839705087;
TLS-RPT
PassPublishedTLS failure reports have somewhere to go.
v=TLSRPTv1; rua=mailto:mta-sts@zapier.com;
BIMI
PassPublishedLogo record found and DMARC qualifies. Yahoo shows it from the record; Gmail and Apple Mail also need a VMC or CMC certificate (the a= tag).
v=BIMI1; l=https://cdn.zapier.com/storage/files/4913356ce8fc5df09a9a1aaba7d0e5bb.svg;
DNSSEC
OptionalNot signedOptional. Signing the zone protects every record in this report from tampering.
2 · Tools visible in DNS
| Layer | Tool | Evidence |
|---|---|---|
| Mailbox | Google Workspace | MX aspmx.l.google.com |
| Marketing | Mailchimp | DKIM mandrill._domainkey |
| Marketing | HubSpot | SPF include:7462085.spf03.hubspotemail.net |
| Transactional | SendGrid | DKIM s1._domainkey → s1.domainkey.u23630585.wl086.sendgrid.net |
| Transactional | Postmark | DKIM pm._domainkey |
| Transactional | Mailgun | SPF include:mailgun.org |
| Support | Zendesk | SPF include:mail.zendesk.com |
| DMARC reporting | Postmark DMARC Digests | DMARC rua=mailto:…@dmarc.postmarkapp.com |
Only tools that leave a DNS trace appear. A shared DKIM selector is attributed only when its CNAME target names the vendor.
3 · Sender requirements (Google, Yahoo, Microsoft)
| Requirement | Applies to | Status | Note |
|---|---|---|---|
| Authenticate with SPF or DKIM | GoogleYahooMicrosoft | Verified | At least one method is in place. |
| Bulk senders: both SPF and DKIM | GoogleYahoo | Verified | Both are present. |
| Publish a DMARC record (p=none is enough) | GoogleYahooMicrosoft | Verified | Policy is p=reject. |
| From: domain aligns with SPF or DKIM | GoogleYahooMicrosoft | Not checkable here | Needs a real message. The Send-a-Test report will check this. |
| Valid forward and reverse DNS for sending IPs | GoogleYahoo | Not checkable here | Depends on the sending server, not the domain. |
| Encrypt in transit (TLS) | GoogleYahoo | Verified | MTA-STS shows inbound TLS is required; outbound depends on your sending tool. |
| One-click unsubscribe (RFC 8058) for marketing mail | GoogleYahoo | Not checkable here | A message header, not a DNS record. Microsoft recommends it rather than requiring it. |
| Spam complaint rate under 0.1% (0.3% is the hard limit) | GoogleYahoo | Not checkable here | Read it in Google Postmaster Tools and Yahoo Sender Hub. Google’s target is 0.1%; 0.3% is where enforcement starts. |
4 · What to fix, in order
-
P3
Sign the zone with DNSSEC
Protects every record in this report from being swapped in transit. Two steps: enable signing at your DNS host (one switch at Cloudflare and most others), then add the DS record it gives you at your registrar.
Publish atzapier.com
Appendix · Raw DNS answers
| Name | Type | Answer |
|---|---|---|
| zapier.com | MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 alt3.aspmx.l.google.com 50 alt4.aspmx.l.google.com 60 ms74255568.msv1.invalid 70 noreply.qemailserver.com |
| zapier.com | A | 108.157.238.4 108.157.238.19 108.157.238.22 108.157.238.115 |
| zapier.com | TXT | v=spf1 include:_spf.google.com include:mailgun.org include:7462085.spf03.hubspotemail.net include:mail.zendesk.com include:_spf.qualtrics.com -all (+ 51 other TXT records: site-verification tokens and the like, omitted) |
| _dmarc.zapier.com | TXT | v=DMARC1; p=reject; pct=100; rua=mailto:re+imuzho2gzgl@dmarc.postmarkapp.com,mailto:dmarc_agg@dmarc.everest.email; ruf=mailto:dmarc_fr@dmarc.everest.email; sp=reject; aspf=r; adkim=r; |
| <selector>._domainkey.zapier.com | TXT | google → key published s1 → CNAME s1.domainkey.u23630585.wl086.sendgrid.net s2 → CNAME s2.domainkey.u23630585.wl086.sendgrid.net smtp → key published mandrill → key published pm → key published |
| _mta-sts.zapier.com | TXT | v=STSv1;id=1585839705087; |
| _smtp._tls.zapier.com | TXT | v=TLSRPTv1; rua=mailto:mta-sts@zapier.com; |
| default._bimi.zapier.com | TXT | v=BIMI1; l=https://cdn.zapier.com/storage/files/4913356ce8fc5df09a9a1aaba7d0e5bb.svg; |