amazonalexa.com
Needs work, with 3 things to fix
amazonalexa.com 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.
Checked 2026-10-04 02:11 UTC · fresh check
All checks
MXCan servers find your inbox?Mail relies on implicit A recordNeeds attention
- Warning: Mail relies on implicit A record
amazonalexa.com has no MX records, so senders fall back to its A/AAAA address (RFC 5321 implicit MX). Publish an explicit MX record, or a null MX ("0 .") if the domain should not receive mail.
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 amazonalexa.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 amazonalexa.com.
DMARCWhat happens to fakes?External DMARC report address is not authorizedNeeds attention
- Warning: External DMARC report address is not authorized
Reports go to dmarc.amazon.com, which is outside amazonalexa.com. RFC 7489 requires that domain to publish a valid v=DMARC1 TXT record at amazonalexa.com._report._dmarc.dmarc.amazon.com; without it receivers will not send you aggregate reports. Your report provider normally publishes this for you.
AlignmentDoes it match your From?SPF alignment is unknownInfo
- Info: SPF alignment is unknown
The SPF record of amazonalexa.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.amazonalexa.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.amazonalexa.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.amazonalexa.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
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to amazonalexa.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.amazonalexa.com
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@amazonalexa.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.amazonalexa.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.amazonalexa.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://amazonalexa.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.amazonalexa.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.