Needs work, with 2 things to fix

adobe.com scored 62/100 (grade C). The main issues are no SPF record and DKIM key shorter than 2048 bits. Detected senders: Google Workspace and Microsoft 365.

Checked 2026-10-04 02:02 UTC · fresh check

4 passed1 needs attention1 failing2 for informationDetected senders: Google Workspace, Microsoft 365

Fix this firstThe change with the biggest effect

Publish an SPF record

Lists the sending services detected for adobe.com (Google Workspace, Microsoft 365) and rejects everything else. Add any other service that sends as adobe.com before publishing. Changes: Added include:_spf.google.com for Google Workspace. Added include:spf.protection.outlook.com for Microsoft 365.

TypeTXT

Name / Host

adobe.com

Some DNS providers want “@” here instead of the full domain.

Value

v=spf1 include:_spf.google.com include:spf.protection.outlook.com -all

How to apply it

Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
Add a new TXT record with the name and value above.
Save, then come back and re-check. DNS changes can take up to a few hours to show.

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?No SPF recordFailing

Fail: No SPF record
adobe.com publishes no TXT record starting with "v=spf1", so receivers cannot tell which servers may send mail for it. Publish one SPF record listing every service that sends as adobe.com.
How to fix this

DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention

Warning: DKIM key shorter than 2048 bits
selector2 (1024-bit), k1 (1024-bit), s2 (1024-bit) uses an RSA key below 2048 bits. Short keys can be factored and some receivers treat them as weak. Rotate to a 2048-bit key at your sending provider.
Pass: DKIM key published
adobe.com publishes a DKIM key under google, selector2, k1, s1, s2, default.

DMARCWhat happens to fakes?No issues foundPass

Nothing to report.

AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?No issues foundPass

Nothing to report.

MTA-STSIs mail to you encrypted?No MTA-STS recordInfo

Info: No MTA-STS record
No MTA-STS record at _mta-sts.adobe.com. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
How to fix this

TLS-RPTWill you hear about failures?No TLS-RPT recordInfo

Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.adobe.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this

Other fixes

Publish the MTA-STS recordTXT

Tells sending servers that adobe.com publishes an MTA-STS policy at https://mta-sts.adobe.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT

Name / Host

_mta-sts.adobe.com

Some DNS providers want just “_mta-sts” here.

Value

v=STSv1; id=202610040202

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.adobe.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location

https://mta-sts.adobe.com/.well-known/mta-sts.txt

Contents

version: STSv1
mode: testing
mx: adobe-com.mail.protection.outlook.com
mx: adobe.mail.protection.outlook.com
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to adobe.com, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.

Applies to: _smtp._tls.adobe.com

Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@adobe.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.adobe.com with the value v=TLSRPTv1; rua=mailto:<that address>.