Apex, subdomain, or URL. We figure it out.

Results for

meilisearch.com

Email authentication

The basics are in place but can be hardened.

  • 3Pass
  • 1Warning
  • 0Fail
  • 2Not set

SPF

Warning

Authorizes which servers may send mail for the domain

SPF is published but could be tightened.

Policy
-all
DNS lookups
9 / 10
  • Ends in -all (hardfail): unauthorized senders are rejected.
  • Uses 9 of 10 allowed DNS lookups. Close to the limit.
v=spf1 a mx include:_spf.google.com include:25945010.spf04.hubspotemail.net include:mailgun.org -all

DKIM

Pass

Cryptographically signs outgoing mail (best-effort selector probe)

DKIM key published for 1 known selector.

Selectors
google
  • Found a DKIM key at google._domainkey.meilisearch.com

DMARC

Pass

Tells receivers what to do with mail that fails SPF and DKIM

DMARC is enforced.

Policy
p=reject
Coverage
100%
  • Policy p=reject: failing mail is rejected outright.
  • Aggregate reports (rua) are configured.
v=DMARC1; p=reject; rua=mailto:[email protected]; pct=100;

MTA-STS

Not set

Enforces TLS for inbound mail and prevents downgrade attacks

No MTA-STS policy. Inbound mail can be delivered without TLS.

TLS-RPT

Not set

Receives reports about TLS delivery failures

No TLS-RPT record. You get no reports about failed TLS delivery.

BIMI

Pass

Displays your verified brand logo in supporting inboxes

BIMI is published.

Logo
https://raw.githubusercontent.com/meilisearch/meilisearch/refs/heads/main/assets/logo.svg
  • A logo (l=) is published.
v=BIMI1;l=https://raw.githubusercontent.com/meilisearch/meilisearch/refs/heads/main/assets/logo.svg

Checks query live DNS over Cloudflare and the public MTA-STS policy endpoint. DKIM selectors cannot be listed from DNS, so DKIM detection probes common provider selectors only.