AWS SES keep saying: BIMI record not found or configured without default selector

Question

I try to follow every detail on https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-bimi.html to set up BIMI for my domain identities **hype.studio** and **hype-group.com**.  Checked all "prerequisites" are done.

I verified SPF, DKIM, DMARC on multiple tools.

And also verified to ensure BIMI setups are all ok on https://bimigroup.org/bimi-generator and also other tools.

Waited over 72 hours.

And I still get this "**BIMI record not found or configured without default selector**" from SES's Virtual Deliverability Manager advisor. It's quite frustrating that it does not show more details.

re:Post Agent · Answer

The issue you're experiencing with AWS SES reporting "BIMI record not found or configured without default selector" despite following the documentation and verifying your setup through other tools is indeed frustrating. However, there are a few potential solutions and checks you can perform:

1. Double-check your BIMI record: Ensure you have added a TXT record for "default._bimi" in your domain's DNS settings. The value should be "v=BIMI1" followed by your BIMI-specific information.

2. Verify DNS propagation: Although you've waited over 72 hours, sometimes DNS changes can take longer to propagate fully. You can use various online DNS lookup tools to check if the BIMI record is visible across different DNS servers.

3. Check subdomain configuration: If you're using a subdomain for your MAIL FROM domain, make sure you have the necessary DNS records (including SPF and MX records) set up for both the main domain and the MAIL FROM subdomain.

4. Verify DMARC policy: Ensure your DMARC policy is set to either "quarantine" or "reject" with a percentage of 100%. BIMI requires a strong DMARC policy to function correctly.

5. Review SES configuration: Make sure you're not sending from individually verified email addresses on the same domain, as this can interfere with DKIM signing and potentially affect BIMI verification.

6. Consider using a placeholder BIMI record: If you're not ready to implement a full BIMI setup with an SVG logo and Verified Mark Certificate (VMC), you can use a placeholder BIMI record to stop this specific recommendation from appearing. Add a TXT record for "default._bimi" with the value "v=BIMI1" (without additional parameters).

7. Monitor EventBridge events: AWS SES generates events that can be monitored using Amazon EventBridge. You might find more detailed information about the BIMI verification status in these events.

If the issue persists after trying these steps, you may need to contact AWS Support for further assistance, as there could be an issue specific to your SES configuration or account that requires their intervention.

**Sources**  
[AWS SES Advisor can't verify BIMI | AWS re:Post](https://repost.aws/questions/QUqsUuhHpCQlej3V317rwxNQ/aws-ses-advisor-can-t-verify-bimi)  
[How do I solve the 'BIMI record not found or configured without default selector' recommendation in Virtual Delivery Manager? | AWS re:Post](https://repost.aws/questions/QUZ-HYL6J7SFGn1btHl6nP8Q/how-do-i-solve-the-bimi-record-not-found-or-configured-without-default-selector-recommendation-in-virtual-delivery-manager)  
[Troubleshooting DKIM problems in Amazon SES - Amazon Simple Email Service](https://docs.aws.amazon.com/ses/latest/dg/troubleshoot-dkim.html)  
[Monitoring SES events using Amazon EventBridge - Amazon Simple Email Service](https://docs.aws.amazon.com/ses/latest/dg/monitoring-eventbridge.html)

AWS SES keep saying: BIMI record not found or configured without default selector

Add your answer

Relevant content