Needs work, with 2 things to fix

icloud-content.com scored 60/100 (grade C). The main issues are the DMARC record has syntax errors and no DKIM key found for the common selectors, plus 1 more.

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

1 passed1 needs attention1 failing5 for information

Fix this firstThe change with the biggest effect

Set up a DMARC report address

Without a rua address nobody receives aggregate reports, so you cannot see who sends as icloud-content.com or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.

Applies to: _dmarc.icloud-content.com

Get an address that collects DMARC aggregate reports: add icloud-content.com to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.icloud-content.com and add rua=mailto:<that address>, keeping every other tag (p=reject) as it is. 3. A report service on another domain must authorize icloud-content.com; most publish that record for you.

All checks

MXCan servers find your inbox?Domain declares it does not accept mailInfo

Info: Domain declares it does not accept mail
icloud-content.com publishes a null MX (RFC 7505), telling senders it accepts no mail. That is correct for a send-only or parked domain.

SPFWho may send as you?No issues foundPass

Nothing to report.

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 icloud-content.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 icloud-content.com.

DMARCWhat happens to fakes?The DMARC record has syntax errorsFailing

Fail: The DMARC record has syntax errors
The record at _dmarc.icloud-content.com has errors: rua entry "mailto:d.agari.com" is not a mailto: address; ruf entry "mailto:d.agari.com" is not a mailto: address. Receivers ignore or misread such records, so it may not do what you intend.
Warning: No DMARC aggregate report address
Without a rua address you receive no aggregate reports, so you cannot see who sends as your domain or safely tighten the policy.
How to fix this

AlignmentDoes it match your From?SPF alignment is unknownInfo

Info: SPF alignment is unknown
The SPF record of icloud-content.com authorizes no sender (no +ip4, +ip6, +a, +mx, +exists or +ptr term, include of a record that has one, or +all before all), so SPF never passes and cannot align. That is correct for a domain that sends no mail; otherwise DMARC depends on DKIM alone.

BIMICan inboxes show your logo?No BIMI recordInfo

Info: No BIMI record
No BIMI record at default._bimi.icloud-content.com. 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.icloud-content.com. 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.icloud-content.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this

Other fixes

Choose an external TLS report addressinstruction

A domain that accepts no mail has no inbound TLS to report on, so TLS-RPT is optional here; a reporting address on icloud-content.com itself would never receive anything.

Applies to: _smtp._tls.icloud-content.com

icloud-content.com publishes a null MX, so it accepts no mail and cannot receive TLS reports itself. If you want TLS-RPT for it, use an address at another domain that receives mail (or a TLS reporting service), then publish a TXT record at _smtp._tls.icloud-content.com 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.icloud-content.com

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://icloud-content.com/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.icloud-content.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.