Who is allowed to send mail as you
v=spf1 include:_spf.google.com include:amazonses.com include:mail.zendesk.com include:_spf.qemailserver.com include:mktomail.com include:_spf.salesforce.com include:_spf.joinzealot.com -all
Cryptographic signature on every send
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqujZfvcovU6vZxxYRppKFIFnyOdkypYo1G9ZnlKXvBB8Vr5u7CbyswID3IPws3MpDUaFTF78NcvwUaHQplc5OwLtKTzpvCNRf+bV6xATviHe/h4MiffxEDceKodKlvRhajIaTZNyabrWg1oVosbjrgL1wJAm/NjPiRP4zi5jgc4CGMMww5NWhhUdpwUXQygt/Oy8y129JGlgDEMiUqYOnsGlyWc12uODITawzkIQMRlPBRiW9/ij0i/GfbrFgn09Jwu4Z24463oAsipcY4uEqpTT+f/05VH13J7fAyC2YjLvsPIXsDwZaOrdBcDtEsT6dx2hGJnMdANZW+/8/t8OyQIDAQAB
What receivers do when SPF or DKIM fail
v=DMARC1; p=reject; sp=reject; pct=100
Your DMARC record has no aggregate-report address (rua=). You're missing the daily reports that show you which sources are claiming to send as your domain — including spoofers.
Where your inbound mail is delivered
aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.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.