How to set up BIMI with a shared IP?

Email marketer from StackOverflow explains the importance of including the shared IP address or the sending provider's designated domain in your SPF record. They emphasize that failing to do so can cause authentication failures and prevent BIMI from functioning correctly.

Email marketer from Reddit shares that while BIMI technically works on shared IPs, sender reputation is critical. They advise closely monitoring deliverability metrics and warming up the IP properly to prevent logo display issues.

Marketer from Email Geeks shares that for DMARC, you only need aligned pass with either SPF or DKIM, but having both is best practice.

Email marketer from Email Vendor Blog suggests diligently monitoring DMARC reports when using a shared IP for BIMI. This helps identify and address any authentication issues promptly, ensuring a smooth BIMI implementation and logo display.

Marketer from Email Geeks shares that you can get the certificate for just your sub-domain if that's your preference, but the org domain must still be p=q/r for BIMI to work.

Email marketer from GMass states that your DMARC record must be set to either p=quarantine or p=reject in order for BIMI to work.

Email marketer from Mailjet shares that setting up BIMI on a shared IP is feasible if you control your domain's SPF, DKIM, and DMARC records. They recommend working with your email service provider to ensure proper authentication configuration for optimal results.

Marketer from Email Geeks confirms that DMARC and BIMI are domain-based, not IP-based.

Marketer from Email Geeks explains that BIMI requires the org domain to be at p=reject or p=quarantine.

Email marketer from Mailgun says using their platform's monitoring tools for insight into deliverability and sender reputation can greatly benefit a BIMI setup with shared IPs. They recommend closely watching bounce rates and engagement data.

Marketer from Email Geeks shares that you can get the BIMI certificate for just the org domain, and it will be inherited if you publish your BIMI record only at the org domain.

Marketer from Email Geeks mentions that using a shared IP can impact your logo's display because deliverability affects BIMI, even when technical requirements are met.

Email marketer from SparkPost warns that shared IPs can affect sender reputation. To overcome this, monitor IP reputation, implement feedback loops, and work to maintain high engagement rates.

Email marketer from Litmus states that BIMI is domain-based, not IP-based. So, a shared IP address doesn't prevent BIMI from working, as long as you have control over your domain's authentication (SPF, DKIM, DMARC) and a valid VMC.

Email marketer from Sendinblue states that with the proper setup of your domain, DMARC, SPF, and DKIM records, BIMI is achievable on Sendinblue's shared IP's. They recommend engaging with their support to achieve this.

Marketer from Email Geeks explains that `p=reject` is not mandatory for BIMI purposes; `p=quarantine` at 100% adoption rate is sufficient.

Expert from Spam Resource emphasizes the importance of properly warming up a shared IP address before implementing BIMI. He explains that gradual increases in sending volume and consistent engagement are crucial for establishing a positive sender reputation and ensuring BIMI logo display.

Expert from Word to the Wise advises ESPs using shared IPs to provide clear guidance and tools to their customers for implementing BIMI correctly. This includes assisting with SPF/DKIM/DMARC setup and offering monitoring capabilities to ensure compliance and deliverability.

Documentation from DigiCert Knowledge Base emphasizes that BIMI requires a valid DMARC policy set to either 'quarantine' or 'reject.' It mentions that while a dedicated IP isn't strictly necessary, maintaining a good sender reputation is crucial on shared IPs to ensure logo display.

Documentation from Entrust Blog highlights the need for a Verified Mark Certificate (VMC) to display a logo through BIMI. It notes that you can obtain a VMC for your primary domain, even when sending from subdomains on a shared IP, provided your DMARC policy is correctly implemented.

Documentation from BIMI Group Website confirms that BIMI works independently of IP addresses, meaning it's compatible with shared IP environments as long as domain authentication standards (SPF, DKIM, DMARC) are properly configured.

Documentation from dmarcian recommends a phased approach to DMARC deployment, starting with 'p=none' to monitor traffic, then moving to 'p=quarantine' and eventually 'p=reject'. This helps minimize disruption and identify any authentication issues before enforcing a stricter policy.