Question 1

SPF policy is neutral

Accepted Answer

A neutral (?all) policy does little to protect your domain from impersonation. Switch to ~all or -all once all legitimate senders are listed in the record.

Question 2

DKIM signing does not appear to be set up

Accepted Answer

DKIM adds a cryptographic signature so inbox providers can verify your messages were not tampered with in transit. Enable DKIM in your email provider (Google Workspace, Microsoft 365, etc.) and publish the TXT record they provide.

Question 3

Domain protection (DMARC) is not enabled

Accepted Answer

Without DMARC, your domain is easier to impersonate — phishing emails may look like they came from you. Publish a DMARC TXT record at _dmarc.yourdomain, start with p=none for monitoring, then move to quarantine or reject.

Question 4

Brand logo in inbox (BIMI) is not configured

Accepted Answer

BIMI can display your logo beside emails in some clients (e.g. Gmail with a verified mark). This is optional but improves brand recognition. If you want inbox branding, publish a BIMI record with an HTTPS SVG logo and obtain a Verified Mark Certificate (VMC) where required.

Question 5

HTTPS does not appear to be working

Accepted Answer

Modern browsers and some email-related trust checks expect a valid TLS site on your domain. Install a valid SSL certificate and ensure port 443 is reachable.

harba.io

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

harba.io

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?