sendgrid.com
71/100
Mail provider: Google Workspace
| Check | Details | |
|---|---|---|
| MX | ✔ | smtp.google.com |
| SPF | ⚠ | v=spf1 include:sendgrid.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:stspg-customer.com ip4:167.89.60.95 ip4:50.31.36.205 ~all (3 lookups); ~all (softfail) - fine with DMARC; -all is stricter; does not include Google Workspace (include:_spf.google.com) |
| DKIM | ⚠ | Selectors found: s1 (2048-bit+), s2 (1024-bit), smtpapi (1024-bit); upgrade 1024-bit keys to 2048-bit |
| DMARC | ✔ | v=DMARC1; p=reject; sp=reject; pct=100; adkim=r; aspf=r; rua=mailto:dmarc_agg@vali.email,mailto:dmarc_rua@sendgrid.com; ruf=mailto:dmarc@sendgrid.com; fo=1; rf=afrf; ri=86400 |
| MTA-STS | ⚠ | Not set (optional; enforces TLS for mail sent to you) |
| TLS-RPT | ⚠ | Not set (optional; reports TLS delivery failures) |
| BIMI | ✔ | v=BIMI1; l=https://amplify.valimail.com/bimi/twilio/qMjF7wPTroQ-twilio_inc_1020931307.svg; a=https://amplify.valimail.com/bimi/twilio/qMjF7wPTroQ-twilio_inc_1020931307.pem |
How to fix it
- SPF — Update the TXT record at sendgrid.com (keeps your existing senders)
v=spf1 include:sendgrid.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:stspg-customer.com ip4:167.89.60.95 ip4:50.31.36.205 include:_spf.google.com ~all
DNS changes can take up to 24–48 hours. Re-run the check afterwards.
Want it fixed for you? I set up SPF, DKIM and DMARC without breaking your other senders,
with a before/after report.
Get it fixed on Fiverr
Get it fixed on Fiverr
Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 19-page guide, checklist, 20+ providers.