Email authentication
The basics are in place but can be hardened.
Authorizes which servers may send mail for the domain
SPF is published and within limits.
v=spf1 ip4:139.138.57.228/32 ip4:68.232.145.169/32 include:servers.mcsv.net include:helpscoutemail.com include:spf.mandrillapp.com include:_spf.google.com include:sendgrid.net ~allCryptographically signs outgoing mail (best-effort selector probe)
DKIM key published for 5 known selectors.
Tells receivers what to do with mail that fails SPF and DKIM
DMARC is published but not fully enforcing.
v=DMARC1; p=none; pct=100; rua=mailto:[email protected], mailto:[email protected], mailto:[email protected]; ruf=mailto:[email protected], mailto:[email protected], mailto:[email protected]; sp=none; aspf=r;Enforces TLS for inbound mail and prevents downgrade attacks
No MTA-STS policy. Inbound mail can be delivered without TLS.
Receives reports about TLS delivery failures
No TLS-RPT record. You get no reports about failed TLS delivery.
Displays your verified brand logo in supporting inboxes
BIMI is published with caveats.
v=BIMI1; l=https://static.app.alyne.com/assets/images/alyne_logo_square_color.svg; a=;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.