adsrvr.org

adsrvr.org · Last checked 2026-10-04 02:07 UTC

adsrvr.org

Needs work, with 3 things to fix

adsrvr.org scored 72/100 (grade C). The main issues are no DKIM key found for the common selectors and external DMARC report address is not authorized, plus 1 more. Detected senders: Microsoft 365, Amazon SES and Salesforce.

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

2 passed3 need attention0 failing3 for informationDetected senders: Microsoft 365, Amazon SES, Salesforce
Fix this firstThe change with the biggest effect

Reduce SPF DNS lookups

Evaluating SPF for adsrvr.org takes 10 DNS lookups including nested includes; receivers stop at 10 and fail SPF. No detected sending service accounts for these includes; remove each one you no longer send through: thetradedesk.com. Changes: Added include:spf.protection.outlook.com for Microsoft 365. Added include:amazonses.com for Amazon SES. Added include:_spf.salesforce.com for Salesforce.

TypeTXT
Name / Host
adsrvr.org

Some DNS providers want “@” here instead of the full domain.

Value
v=spf1 include:thetradedesk.com include:spf.protection.outlook.com include:amazonses.com include:_spf.salesforce.com -all
Replaces
v=spf1  include:thetradedesk.com -all

How to apply it

  1. Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
  2. Find the existing TXT record with that name and replace its value.
  3. Save, then come back and re-check. DNS changes can take up to a few hours to show.

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?SPF is close to the 10-lookup limitNeeds attention
  • Warning: SPF is close to the 10-lookup limit

    Evaluating the SPF record for adsrvr.org needs 10 of the 10 allowed DNS lookups. Adding one more service, or a provider growing its own record, will break SPF.

    How to fix this
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 adsrvr.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 adsrvr.org.

DMARCWhat happens to fakes?External DMARC report address is not authorizedNeeds attention
  • Warning: External DMARC report address is not authorized

    Reports go to thetradedesk.com, which is outside adsrvr.org. RFC 7489 requires that domain to publish a valid v=DMARC1 TXT record at adsrvr.org._report._dmarc.thetradedesk.com; without it receivers will not send you aggregate reports. Your report provider normally publishes this for you.

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.adsrvr.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.adsrvr.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.adsrvr.org. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

Other fixes

Enable DKIM for Microsoft 365instruction

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

Applies to: selector1._domainkey.adsrvr.org

  1. In Microsoft 365, enable DKIM signing for adsrvr.org: tenant-specific: copy Selector1CNAME/Selector2CNAME from Microsoft 365 Defender > Email authentication > DKIM. Publish exactly the record Microsoft 365 shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://learn.microsoft.com/microsoft-365/security/office-365-security/email-authentication-dkim-configure

Enable DKIM for Microsoft 365instruction

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

Applies to: selector2._domainkey.adsrvr.org

  1. In Microsoft 365, enable DKIM signing for adsrvr.org: tenant-specific: copy Selector1CNAME/Selector2CNAME from Microsoft 365 Defender > Email authentication > DKIM. Publish exactly the record Microsoft 365 shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://learn.microsoft.com/microsoft-365/security/office-365-security/email-authentication-dkim-configure

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 adsrvr.org cannot pass DMARC through DKIM.

Applies to: _domainkey.adsrvr.org

  1. In Amazon SES, enable DKIM signing for adsrvr.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 Salesforceinstruction

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

Applies to: _domainkey.adsrvr.org

  1. In Salesforce, enable DKIM signing for adsrvr.org: account-specific: copy the CNAME/TXT from the Salesforce dashboard. Publish exactly the record Salesforce shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://help.salesforce.com/s/articleView?id=sf.emailadmin_create_secure_dkim.htm

Publish the MTA-STS recordTXT

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

TypeTXT
Name / Host
_mta-sts.adsrvr.org

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

Value
v=STSv1; id=202610040207

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.adsrvr.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.adsrvr.org/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: smtp.secureserver.net
mx: mailstore1.secureserver.net
max_age: 604800

Set up a TLS report addressinstruction

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

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@adsrvr.org, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.adsrvr.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.adsrvr.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://adsrvr.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.adsrvr.org with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.