Question 1

SPF uses softfail (~all)

Accepted Answer

Softfail is acceptable for many teams, but stricter -all is stronger once you are confident every sender is listed. Review includes (Google, Microsoft, CRM, etc.) then consider upgrading to -all.

Question 2

DKIM key may be using older key length

Accepted Answer

Shorter RSA keys are easier to forge; many providers now prefer 2048-bit keys. Rotate to a 2048-bit DKIM key in your mail provider admin console.

Question 3

Your emails may appear less trustworthy because domain protection is not fully enabled

Accepted Answer

DMARC is present but set to p=none — receivers are told to accept failing messages. Impersonation is still possible. After reviewing aggregate reports (rua), tighten policy to p=quarantine then p=reject.

Question 4

Stronger email protection is needed before BIMI

Accepted Answer

BIMI needs stronger email protection before mailbox providers will trust your logo. Move DMARC to quarantine or reject after legitimate mail passes SPF and DKIM, then rescan.

Question 5

Brand logo setup is missing

Accepted Answer

Your domain is not yet set up to show a verified brand logo in supporting inboxes. Publishing a BIMI record alone is not enough — you also need a valid BIMI SVG hosted over HTTPS. Add a BIMI TXT record at default._bimi with v=BIMI1 and l= pointing to your HTTPS SVG logo.

abakusbroker.com

Will your emails land in the inbox instead of spam?

Can people tell a fake email isn't really from you?

Want your logo to show up next to your emails in Gmail and other inboxes?

Email health checker

abakusbroker.com

Will your emails land in the inbox instead of spam?

Can people tell a fake email isn't really from you?

Want your logo to show up next to your emails in Gmail and other inboxes?