Who is allowed to send mail as you
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
Cryptographic signature on every send
No DKIM record found on your domain. DKIM cryptographically signs your outgoing mail so receivers can prove it really came from you. Without it, Gmail and Outlook will mark most of your mail as suspicious or send it straight to spam.
What receivers do when SPF or DKIM fail
v=DMARC1;p=reject;pct=100;rua=mailto:c7xrs-8253@rua.dmarc.emailanalyst.com,mailto:dmarc@dropbox.com
Where your inbound mail is delivered
mxa-001ed902.gslb.pphosted.com, mxb-001ed902.gslb.pphosted.com
Your MX records point to mail servers other than Google's. Because FrostSender connects through Gmail OAuth, Gmail and other inbox providers will treat mail you send as spoofing — outgoing delivery will fail.
Want this fixed at the source?
FrostSender ships with deliverability monitoring built in. Get on the list and we’ll let you know the moment we open access.