Good, with 3 things to fix

adobe.io scored 76/100 (grade B). The main issues are DMARC alignment: SPF alignment is unlikely for third-party senders and DKIM key shorter than 2048 bits, plus 1 more. Detected senders: Amazon SES and Campaign Monitor.

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

1 passed3 need attention0 failing4 for informationDetected senders: Amazon SES, Campaign Monitor

All checks

MXCan servers find your inbox?Mail relies on implicit A recordNeeds attention

Warning: Mail relies on implicit A record
adobe.io has no MX records, so senders fall back to its A/AAAA address (RFC 5321 implicit MX). Publish an explicit MX record, or a null MX ("0 .") if the domain should not receive mail.

SPFWho may send as you?No issues foundPass

Nothing to report.

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

Warning: DKIM key shorter than 2048 bits
cm (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.io publishes a DKIM key under cm.

DMARCWhat happens to fakes?DMARC uses strict alignmentInfo

Info: DMARC uses strict alignment
With adkim=s or aspf=s the DKIM d= domain or the bounce domain must equal the From domain exactly; a subdomain is not enough. Third-party senders that sign or bounce from a subdomain (or their own domain) will then fail DMARC unless they are configured to use your exact domain.

AlignmentDoes it match your From?SPF alignment is unlikely for third-party sendersNeeds attention

Warning: SPF alignment is unlikely for third-party senders
This is a heuristic. Your SPF record authorizes amazonses.com, and such providers normally bounce from their own Return-Path domain or from a subdomain of yours. With aspf=s the Return-Path domain must equal adobe.io exactly, so SPF will not align for mail they send and DMARC depends on DKIM alone. Make sure each provider signs with DKIM as adobe.io.

BIMICan inboxes show your logo?No BIMI recordInfo

Info: No BIMI record
No BIMI record at default._bimi.adobe.io. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.
How to fix this

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

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

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

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

How to fix it

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to adobe.io, 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.io

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

Prepare BIMIinstruction

BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.

Applies to: default._bimi.adobe.io

Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://adobe.io/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.adobe.io with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.