Who is allowed to send mail as you
v=spf1 include:_spf.google.com include:_spf.salesforce.com ~all
Cryptographic signature on every send
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtxnFCcqWqIYO4d/aSTwkLXR0uDHEgZ10AQ8K5JD1Q45vRgCHr0Iq+08az7BweotOgXOIvWAwLbk0RgfCms5L/arEs3Hq5S6takmfweakNylhPMckfs2+nBWm3OjfMGo834WG7g6MyGP4vpCOl8ww0whCUxRTPgRDOg/io+D5E+k6YQJBhCkJqwjx1RnVEtt71jmbs/nwutd7+NaURQMP3bcEMUmG0LWYCOEfnOWyQHBVtcOHb+BZBBO2WfjZgROEygIeUnEZtsPjB+1iJOLYCqwm+lr3sNG4n9ZBdz9UM+fTbaJOnIrt7P9VHz5HurQEQ6eekvNwXP1nhTaUYKoF0wIDAQAB
What receivers do when SPF or DKIM fail
v=DMARC1; p=none; rua=mailto:ipm5uzr@ar.glockapps.com,mailto:ipm2uj7@ar.glockapps.com; ruf=mailto:ipm5uzr@fr.glockapps.com,mailto:ipm2uj7@fr.glockapps.com; fo=1;
Your DMARC policy is "p=none" — monitor-only mode. Inbox providers still respect your SPF/DKIM passes, but failed mail isn't quarantined or rejected. This is fine for the first 2 weeks of a new domain, but you should tighten it once your real sends are clean.
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.