dropbox.com
71/100
Mail provider: Unknown
| Check | Details | |
|---|---|---|
| MX | ✔ | mxa-001ed902.gslb.pphosted.com, mxb-001ed902.gslb.pphosted.com |
| SPF | ✔ | v=spf1 ip4:45.58.64.0/20 ip4:185.45.8.0/22 ip4:162.125.0.0/16 ip4:199.47.216.0/22 ip4:108.160.160.0/20 ip4:205.189.0.0/24 ip4:160.34.15.16/28 ip4:52.5.134.202/32 ip4:205.220.162.87/32 ip4:205.220.174.83/32 ip4:167.89.98.146/32 ip4:167.89.89.46/32 ip4:167.89.96.134/32 ip4:159.183.109.97/32 ip4:149.72.220.85/32 ip4:159.183.15.144/32 ip4:159.183.2.51/32 ip4:159.183.2.58/32 ip6:2620:c6:8000::/48 include:amazonses.com include:_spf.google.com include:mail.zendesk.com include:mktomail.com include:rp.oracleemaildelivery.com exists:%{i}._spf.mta.salesforce.com ~all (7 lookups); ~all (softfail) - fine with DMARC; -all is stricter |
| DKIM | ✖ | No DKIM key found on common selectors (a custom selector may exist - check a sent email's DKIM-Signature: s= header). |
| DMARC | ✔ | v=DMARC1;p=reject;pct=100;rua=mailto:c7xrs-8253@rua.dmarc.emailanalyst.com,mailto:dmarc@dropbox.com |
| 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://cfl.dropboxstatic.com/static/metaserver/static/images/emails/bimi/order_400664024_logo.svg;a=https://cfl.dropboxstatic.com/static/metaserver/static/images/emails/bimi/dropbox_inc.pem |
How to fix it
- DKIM — Turn on DKIM signing in your email provider and publish the TXT/CNAME it gives you
(record value comes from your provider's admin panel)
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.