Good, with 3 things to fix

example.com scored 76/100 (grade B). The main issues are DMARC alignment: DKIM alignment is unlikely under adkim=s and DKIM key revoked, plus 1 more.

Checked 2026-10-03 22:20 UTC

1 passed3 need attention0 failing4 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 example.com or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.

Applies to: _dmarc.example.com

Get an address that collects DMARC aggregate reports: add example.com to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.example.com and add rua=mailto:<that address>, keeping every other tag (p=reject, sp=reject) as it is. 3. A report service on another domain must authorize example.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
example.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?DKIM key revokedNeeds attention

Warning: DKIM key revoked
google, selector1, selector2, k1, k2, k3, s1, s2, mail, default, dkim, smtp, mandrill, pm, pm-bounces, mg, mailo, krs, email, sendinblue, brevo, hs1, hs2, amazonses, ses, zendesk1, zendesk2, fd, fd2, protonmail, protonmail2, protonmail3, zoho, everlytickey1, everlytickey2, sig1, cm, mxvault, turbo-smtp, sparkpost, scph0123, kl, kl2, resend, intercom, cf2024-1, cf-bounce publishes an empty p= tag, so any mail still signed with that selector fails DKIM. That is correct after a key rotation; otherwise publish the current key or stop signing with this selector.

DMARCWhat happens to fakes?No DMARC aggregate report addressNeeds attention

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
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?DKIM alignment is unlikely under adkim=sNeeds attention

Warning: DKIM alignment is unlikely under adkim=s
This is a heuristic. No DKIM key was found at example.com under the selectors we probed, and adkim=s requires the signing d= domain to equal example.com exactly. If your mail is signed with a provider's domain or a subdomain, DKIM will not align. A key may exist under a selector we did not try; send a test message to confirm.
Info: SPF alignment is unknown
The SPF record of example.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.example.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.example.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.example.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 example.com itself would never receive anything.

Applies to: _smtp._tls.example.com

example.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.example.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.example.com