Who is allowed to send mail as you
v=spf1 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.0.0/16 ip4:129.145.74.12 include:_spf.google.com include:mailsenders.netsuite.com include:_spf2.intuit.com include:_spf.qualtrics.com ip4:199.33.145.1 ip4:199.33.145.32 ip4:35.176.132.251 ip4:52.60.115.116 ~all
Cryptographic signature on every send
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCax9niz/ztmrk0lxV13XNCKVttq7LZqAL+WbNH+/pKI0AVKSccQEry6xqk+OtmAX1gWkjaKW7Z77dURIDWcFCsVOM07Jaky4hpZCs8SjtIDN8nmp0ao1PCEVcfFbVDu9Q4E9rqUxHg9BhnK02fTIsvI0uH/khHGFUnVS7jB3gFkQIDAQAB
What receivers do when SPF or DKIM fail
v=DMARC1; p=reject; rua=mailto:19ezfriw@ag.dmarcian.com,mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:19ezfriw@fr.dmarcian.com,mailto:dmarc_ruf@emaildefense.proofpoint.com;
Where your inbound mail is delivered
mx1.intuit.iphmx.com, mx2.intuit.iphmx.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.