Needs work, with 3 things to fix

me.com scored 72/100 (grade C). The main issues are no DKIM key found for the common selectors and BIMI record is malformed, plus 1 more.

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

1 passed3 need attention0 failing4 for information

All checks

MXCan servers find your inbox?MX host is a CNAMENeeds attention

Warning: MX host is a CNAME
RFC 2181 forbids an MX target that is an alias. Some senders refuse or delay delivery to mx01.mail.icloud.com, mx02.mail.icloud.com. Point the MX at the canonical hostname instead.

SPFWho may send as you?SPF ends in softfail (~all)Info

Info: SPF ends in softfail (~all)
"~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.

DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention

Warning: No DKIM key found for the common selectors
None of the 47 selectors probed under me.com publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for me.com.

DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo

Info: DMARC policy is quarantine; consider reject
Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.
How to fix this

AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?BIMI record is malformedNeeds attention

Warning: BIMI record is malformed
The BIMI record at default._bimi.me.com is invalid: the l= tag (SVG logo URL) is missing.

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

Info: No MTA-STS record
No MTA-STS record at _mta-sts.me.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.me.com. 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

Strengthen the DMARC policyTXT

Rejects mail that fails DMARC, the strongest protection against spoofing. Changes: Subdomains move one step, from sp=quarantine to the domain policy (p=reject).

TypeTXT

Name / Host

_dmarc.me.com

Some DNS providers want just “_dmarc” here.

Value

v=DMARC1; p=reject; rua=mailto:d@rua.agari.com; adkim=r; aspf=r

Replaces

v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com

Publish the MTA-STS recordTXT

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

TypeTXT

Name / Host

_mta-sts.me.com

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

Value

v=STSv1; id=202610040217

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.me.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.me.com/.well-known/mta-sts.txt

Contents

version: STSv1
mode: testing
mx: mx01.mail.icloud.com
mx: mx02.mail.icloud.com
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to me.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.me.com

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