All four checks pass. Your domain is set up to land in the inbox.
Who is allowed to send mail as you
v=spf1 include:_spf.google.com include:amazonses.com include:mktomail.com include:mail.zendesk.com include:_spf.qualtrics.com include:servers.mcsv.net include:_spf.salesforce.com ~all
Cryptographic signature on every send
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDvP10IFpm64QGHLT1J6okZccTrvYFQTYgjOcXurjKxhhvHQMQZ2PK/q+vpqR2qAGWgc9yqJKtXmTs1Ef9J2JZ7hPuKQLjFXXrwumLY1Lki7NzEunV6LwLj/rZ+OMm3G92pyuAIHg/49fBOcQyyimKthzKoDyZaY2v9lLphZQLGLQIDAQAB
What receivers do when SPF or DKIM fail
v=DMARC1; p=reject; rua=mailto:dmarc@plaid.com,mailto:re+tweoobejql7@dmarc.postmarkapp.com; ruf=mailto:dmarc@plaid.com
Where your inbound mail is delivered
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com
Want it to stay this way?
FrostSender ships with deliverability monitoring built in. Get on the list and we’ll let you know the moment we open access.