aol.com
Needs work, with 2 things to fix
aol.com scored 72/100 (grade C). The main issues are no DKIM key found for the common selectors and SPF ends in neutral (?all), plus 1 more.
Checked 2026-10-04 02:10 UTC · fresh check
All checks
MXCan servers find your inbox?Only one MX hostInfo
- Info: Only one MX host
All mail for aol.com goes to mx-aol.mail.gm0.yahoodns.net. Most hosted providers make that one name highly available; if you run your own server, consider a backup MX.
SPFWho may send as you?SPF uses the ptr mechanismNeeds attention
- Warning: SPF uses the ptr mechanism
The SPF record of _spf.mail.yahoo.com uses ptr. RFC 7208 §5.5 says ptr "SHOULD NOT be used": it is slow, unreliable, and some receivers ignore it. Replace it with ip4/ip6 ranges or an include from your provider.
- Warning: SPF ends in neutral (?all)
"?all" tells receivers to treat mail from unlisted servers as neither pass nor fail, so SPF gives no protection. End the record with "-all" or "~all".
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 aol.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 aol.com.
DMARCWhat happens to fakes?No issues foundPass
Nothing to report.
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.aol.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.aol.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.aol.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
Publish the MTA-STS recordTXT
Tells sending servers that aol.com publishes an MTA-STS policy at https://mta-sts.aol.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.aol.com
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040210
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.aol.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.aol.com/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: mx-aol.mail.gm0.yahoodns.net max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to aol.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.aol.com
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@aol.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.aol.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.aol.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://aol.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.aol.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.