docusign.com email setup: SPF, DKIM, DMARC & tools

You are viewing a shared snapshot read on . It may differ from what DNS says now.

Domain

docusign.com

The three core checks pass. What is missing is the transport and trust layer around them.

6 of 8 checks pass · 4 tools visible in DNS · nothing urgent

Grade B

SPFValid, hard fail20/20

DKIM4 keys found15/15

DMARCEnforced (p=reject)30/30

MX2 hosts10/10

MTA-STSNot published0/10

TLS-RPTNot published0/5

BIMIPublished5/5

DNSSECValidated5/5

1 · Authentication and transport

SPF

PassValid, hard fail

Anything not on the list is rejected. The strongest setting.

v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ip4:205.220.176.129 ip4:205.220.164.129 ip4:205.220.166.129 ip4:205.220.177.61 include:_spf.google.com -all

DKIM

Pass4 keys found

Selectors google, s1, s2, mandrill publish a public key. 2 of them point at a vendor by CNAME.

google._domainkey, s1._domainkey, s2._domainkey, mandrill._domainkey

DMARC

PassEnforced (p=reject)

Failing mail is rejected. This is the finish line.

v=DMARC1; p=reject; sp=reject; adkim=r; aspf=r; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com; fo=1;

MX

Pass2 hosts

More than one receiving server, so a single outage does not bounce mail.

10 mxa-00567a01.gslb.pphosted.com
20 mxb-00567a01.gslb.pphosted.com

MTA-STS

ReviewNot published

Sending servers cannot tell that this domain requires TLS, so inbound mail can be downgraded to plain text by anyone on the path.

TLS-RPT

OptionalNot published

Nobody is told when TLS to this domain fails. Cheap to add once MTA-STS is in place.

BIMI

PassPublished

Logo 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://bimi.docusign.com/docusign-bimi.svg; a=https://bimi.docusign.com/docusign-bimi.pem;

DNSSEC

PassValidated

The resolver validated the zone, so the records above cannot be silently swapped in transit.

2 · Tools visible in DNS

Layer	Tool	Evidence
Mailbox	Google Workspace	SPF include:_spf.google.com
Gateway	Proofpoint	MX mxa-00567a01.gslb.pphosted.com
Marketing	Mailchimp	DKIM mandrill._domainkey
Transactional	SendGrid	DKIM s1._domainkey → s1.domainkey.u904041.wl042.sendgrid.net

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	Not checkable here	Outbound TLS depends on your sending tool; MTA-STS would cover inbound.
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
Publish MTA-STS (record and policy file)

Tells sending servers to require TLS to your MX hosts, which prevents downgrade attacks. The TXT record alone does nothing: the policy file must be served over HTTPS at mta-sts.docusign.com. Start in testing mode, watch TLS-RPT, then switch to enforce.

Publish at_mta-sts.docusign.com and https://mta-sts.docusign.com/.well-known/mta-sts.txt
```
TXT  v=STSv1; id=2026100401

mta-sts.txt:
version: STSv1
mode: testing
mx: mxa-00567a01.gslb.pphosted.com
mx: mxb-00567a01.gslb.pphosted.com
max_age: 86400
```
P3
Publish TLS-RPT

You get a report when TLS delivery to your domain fails; this is what notices a downgrade that MTA-STS is meant to prevent. The address must exist.

Publish at_smtp._tls.docusign.com
```
v=TLSRPTv1; rua=mailto:tls-rpt@docusign.com
```

Appendix · Raw DNS answers

Name	Type	Answer
docusign.com	MX	10 mxa-00567a01.gslb.pphosted.com 20 mxb-00567a01.gslb.pphosted.com
docusign.com	A	3.33.186.135 15.197.167.90
docusign.com	TXT	v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ip4:205.220.176.129 ip4:205.220.164.129 ip4:205.220.166.129 ip4:205.220.177.61 include:_spf.google.com -all (+ 57 other TXT records: site-verification tokens and the like, omitted)
_dmarc.docusign.com	TXT	v=DMARC1; p=reject; sp=reject; adkim=r; aspf=r; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com; fo=1;
<selector>._domainkey.docusign.com	TXT	google → key published s1 → CNAME s1.domainkey.u904041.wl042.sendgrid.net s2 → CNAME s2.domainkey.u904041.wl042.sendgrid.net mandrill → key published
_mta-sts.docusign.com	TXT	no record
_smtp._tls.docusign.com	TXT	no record
default._bimi.docusign.com	TXT	v=BIMI1; l=https://bimi.docusign.com/docusign-bimi.svg; a=https://bimi.docusign.com/docusign-bimi.pem;

About this report

The Email Stack reads public DNS for well-known domains and publishes the result as a report, the same one anyone can generate for any domain at /report. It is a point-in-time read: records change, and a domain that scores B today may score differently next month. The "Re-run live" button reads DNS again in your browser.

Scores weigh SPF 20, DKIM 15, DMARC 30, MX 10, MTA-STS 10, TLS-RPT 5, BIMI 5 and DNSSEC 5. Tools are named only when a DNS record names the vendor; a shared DKIM selector counts only when its CNAME target does. Message-level requirements such as alignment and one-click unsubscribe cannot be read from DNS and are marked as such, never guessed. Method: how we detect tools.

Own this domain and see something wrong? DNS is the source; fix the record and the next read will show it. Questions to hello@theemailstack.com.

docusign.comemail setup