Who is allowed to send mail as you
v=spf1 include:_spf.google.com include:spf.mailjet.com include:mail.zendesk.com include:_spf.salesforce.com include:mailgun.org ?all
Your SPF record doesn't end with an enforcement mechanism. Unauthorized senders won't be challenged.
Cryptographic signature on every send
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnQsokxGfCyEVwI0QjSDWwS7tAYrTFmQSvNrZC86OvaDus+08Se37veOOMbhl3B9w+Vj9fhXD19/6rUNj/kCQcPjhCzisXV8sWqWHSvkIkUzK0lz1nlVfQq5dUvfOJwE/luOrm915Ta7CmpQgfkGXCUy/qSeiAV2YhvhhTRF9ZjdgHf5tbfzBBXz2GTp9m7mO76XFAvnzA+SCBlHCWT8Ff+Yayi1DoCS0qbw4a/OJLBxKnpd2pMnbh5R9Dys17FSGvMTo4nGh6XtBDtTl7mhNeWgIjtKEHiC4fRxsTfyZZnkva37Zhyc+uY7M6iWM/S5Gnn515SkHvHYRsr/m06+oIQIDAQAB
What receivers do when SPF or DKIM fail
v=DMARC1; p=reject; sp=none; rua=mailto:dmarc-reports@webflow.com,mailto:re+9a4f4489f1fa@inbound.dmarcdigests.com,mailto:1901099@dmarc.mailgun.org,mailto:eaa0e9d1@inbox.ondmarc.com; ruf=mailto:1901099@dmarc.mailgun.org,mailto:eaa0e9d1@inbox.ondmarc.com; aspf=r; pct=100; fo=1; ri=3600
Where your inbound mail is delivered
aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com
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.