doi.org

doi.org · Last checked 2026-10-04 02:05 UTC

doi.org

Good, with 1 thing to fix

doi.org scored 88/100 (grade B). The main issue is no DKIM key found for the common selectors. Detected senders: Amazon SES and Zoho Mail.

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

2 passed1 needs attention0 failing5 for informationDetected senders: Amazon SES, Zoho Mail

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

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 doi.org 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 doi.org.

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?No BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.doi.org. 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.doi.org. 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.doi.org. 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.doi.org

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=reject; rua=mailto:4346ea155d494c77bb5cb3dfcf540754@dmarc-reports.cloudflare.net; adkim=r; aspf=r
Replaces
v=DMARC1; p=quarantine; pct=100; rua=mailto:4346ea155d494c77bb5cb3dfcf540754@dmarc-reports.cloudflare.net; sp=quarantine;aspf=r;adkim=r;ri=86400

Enable DKIM for Amazon SESinstruction

Amazon SES generates the DKIM key for each account, so the exact record must come from Amazon SES. Without DKIM, mail it sends for doi.org cannot pass DMARC through DKIM.

Applies to: _domainkey.doi.org

  1. In Amazon SES, enable DKIM signing for doi.org: account-specific: copy the CNAME/TXT from the Amazon SES dashboard. Publish exactly the record Amazon SES shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dkim-easy.html

Enable DKIM for Zoho Mailinstruction

Zoho Mail generates the DKIM key for each account, so the exact record must come from Zoho Mail. Without DKIM, mail it sends for doi.org cannot pass DMARC through DKIM.

Applies to: zoho._domainkey.doi.org

  1. In Zoho Mail, enable DKIM signing for doi.org: account-specific: copy the CNAME/TXT from the Zoho Mail dashboard. Publish exactly the record Zoho Mail shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://www.zoho.com/mail/help/adminconsole/dkim-configuration.html

Publish the MTA-STS recordTXT

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

TypeTXT
Name / Host
_mta-sts.doi.org

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

Value
v=STSv1; id=202610040205

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.doi.org. 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.doi.org/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: mx.zoho.eu
mx: mx2.zoho.eu
mx: mx3.zoho.eu
max_age: 604800

Set up a TLS report addressinstruction

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

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@doi.org, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.doi.org 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.doi.org

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